← previous blocknext block →recent activity
Analyzing
Block #76,211,182
9 transactions · 8 stateful · 2026-05-22 06:56:31 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,211,182 · 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
1w02w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0xfe2bac2b…2cec
0x065c9d…c394
4 touches
1 conflict
0x46725fba…84e9
0x065c9d…c394
2 touches
0 conflicts
0x80998d48…9518
0x065c9d…c394
2 touches
0 conflicts
0x98e46ca2…76dc
0x065c9d…c394
2 touches
0 conflicts
0xbde5a0e3…927c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity