← previous blocknext block →recent activity
Analyzing
Block #92,049,315
17 transactions · 13 stateful · 2026-07-31 23:38:56 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,049,315 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x88bba329…20cd
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x581f6cfb…49a4
0x065c9d…c394
2 touches
0 conflicts
0x63eec40e…b8f7
0x065c9d…c394
2 touches
0 conflicts
0x89ed4652…926b
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
0x065c9d…c394
2 touches
0 conflicts
0xea4053bb…4002
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x88bba329b5…1720cd
Audit this contract →
← previous block·next block →recent activity