← previous blocknext block →recent activity
Analyzing
Block #76,559,418
13 transactions · 13 stateful · 2026-05-23 21:35:45 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,559,418 · 13 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
1w02w03w14w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xf282c2b3…28b4
0xa6afd3…d132
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xa17ec269…7cdd
0x1d1325…2305
2 touches
0 conflicts
0xa605468c…1bfc
0x1d1325…2305
2 touches
0 conflicts
0xc8525006…2b45
0x1d1325…2305
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 0xdfa159d0ee…971576
Audit this contract →
← previous block·next block →recent activity