← previous blocknext block →recent activity
Analyzing
Block #76,239,085
9 transactions · 8 stateful · 2026-05-22 10:02:52 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,239,085 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x97114791…8a89
0x065c9d…c394
3 touches
1 conflict
0xaabaddd6…f3c4
0x065c9d…c394
3 touches
1 conflict
0x066998d2…b0e9
0x065c9d…c394
3 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
3 conflicts on slot 0xba38536db1…342b7d
Audit this contract →
← previous block·next block →recent activity