← previous blocknext block →recent activity
Analyzing
Block #76,109,249
9 transactions · 8 stateful · 2026-05-21 19:37:59 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,109,249 · 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
1w03w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x0028002c…1a86
0x065c9d…c394
2 touches
0 conflicts
0x19e4b82d…f372
0x065c9d…c394
2 touches
0 conflicts
0x8da42638…74dc
0x065c9d…c394
2 touches
0 conflicts
0x9c7c95ab…7638
0x065c9d…c394
2 touches
0 conflicts
0xb95b1d59…6a97
0x065c9d…c394
2 touches
0 conflicts
0xbe18f956…3bde
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity