← previous blocknext block →recent activity
Analyzing
Block #76,262,299
9 transactions · 6 stateful · 2026-05-22 12:37:12 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,262,299 · 9 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc2f1e4f8…1ba4
0x065c9d…c394
3 touches
1 conflict
0x8f5c41d6…6784
0x065c9d…c394
3 touches
1 conflict
0x88ce7bc5…8cac
0x065c9d…c394
3 touches
1 conflict
0xbc04563b…3338
0x065c9d…c394
3 touches
1 conflict
0xd409887f…b053
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 0xfe2bac2b2f…482cec
Audit this contract →
← previous block·next block →recent activity