← previous blocknext block →recent activity
Analyzing
Block #81,626,035
9 transactions · 9 stateful · 2026-06-16 08:45:54 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #81,626,035 · 9 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
1w02w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x43e29fdd…81b8
0x065c9d…c394
4 touches
1 conflict
0x21e32684…83b0
0x065c9d…c394
3 touches
1 conflict
0x7fd442d6…191f
0x065c9d…c394
3 touches
1 conflict
0x85264c2d…bd35
0x065c9d…c394
2 touches
0 conflicts
0x9cfcd540…3ebb
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
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