← previous blocknext block →recent activity
Analyzing
Block #76,262,053
12 transactions · 10 stateful · 2026-05-22 12:35:34 UTC
Parallelism
67/100
Blocked
60%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,262,053 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w36w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa605468c…1bfc
0x1d1325…2305
6 touches
3 conflicts
0xf85c75bc…00b5
0xa6afd3…d132
6 touches
3 conflicts
0x1fff6dcb…b3f4
0xc8689a…ee79
6 touches
3 conflicts
0x236c5b2c…da1c
0x065c9d…c394
5 touches
3 conflicts
0x90a94033…a85e
0x065c9d…c394
5 touches
3 conflicts
0xc8525006…2b45
0x1d1325…2305
4 touches
2 conflicts
0xa17ec269…7cdd
0x1d1325…2305
4 touches
2 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