← previous blocknext block →recent activity
Analyzing
Block #76,677,149
13 transactions · 12 stateful · 2026-05-24 10:39:29 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,677,149 · 13 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
1w02w15w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x196a5b88…72a3
0x065c9d…c394
4 touches
1 conflict
0x2c0e60af…21eb
0x065c9d…c394
4 touches
1 conflict
0x5b1291fe…5a27
0x065c9d…c394
4 touches
1 conflict
0x63649a2c…a34a
0x065c9d…c394
4 touches
1 conflict
0xca073497…3a50
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0xf65bc1dc…c99b
0x065c9d…c394
4 touches
1 conflict
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