← previous blocknext block →recent activity
Analyzing
Block #76,033,962
19 transactions · 17 stateful · 2026-05-21 11:15:55 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,033,962 · 19 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
1w03w16w17w217w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0xd10071bc…084b
0x065c9d…c394
3 touches
1 conflict
0x10224300…74d6
0x065c9d…c394
2 touches
0 conflicts
0x24e18009…bc2c
0x065c9d…c394
2 touches
0 conflicts
0xdfa8cefc…8d2e
0x065c9d…c394
2 touches
0 conflicts
0xe1280f48…eed1
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity