Portfolio view
- WalletUSDC balance 3,700 RPC read at 1,100
- LendingUSDC supplied 10,000 Subgraph at 1,100
- BorrowHealth factor 3.00 −2,500 Subgraph at 1,100
- Liquidity poolUSDC / EURC · fees 15 6,415 Subgraph at 1,100
- Staking5,000 staked · rewards 35 5,035 Subgraph at 1,100
Activity
- Block 1,100 Repay 500 USDC RPC receipt
0x6d…f2· success - Block 1,099 Swap
- Block 1,098 Rewards accrued
The balance read, indexed entities, and receipt all refer to block 1,100.
How it comes together
- GraphOps service
- Your systems and team
- GraphOps RPC
Send the signed repayment
The user’s wallet signs the transaction, and your app submits it through RPC.
- GraphOps RPC
Confirm inclusion and read the balance
The receipt shows success in block 1,100. A balance read at block 1,100 returns 3,700 USDC.
- GraphOps Subgraphs
Query positions and activity
A query to your Subgraph returns the loan, pool, staking, and activity entities, and its indexing metadata reports block 1,100.
- Your app
Present one consistent view
The index has reached the receipt’s block, so the repayment appears in the feed. Your confirmation policy decides when to mark it final.
ResultThe user sees the repayment, a 3,700 USDC balance, and a 2,500 USDC loan at health factor 3.00, all from block 1,100.
A receipt’s inclusion does not by itself establish finality. Subgraph results follow indexing progress and can change after a reorg.
If the index has not reached the receipt’s block
Show the repayment as pending from its receipt and label positions with their indexed block. Refresh as indexing advances, and do not treat a missing feed entry as a failed transaction.