← previous blocknext block →recent activity
Analyzing
Block #81,632,746
22 transactions · 20 stateful · 2026-06-16 09:30:37 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,632,746 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w07w38w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x91139519…50ad
0xd32edf…ff58
5 touches
3 conflicts
0x511f46a7…edab
0x1b6862…e19c
4 touches
1 conflict
0x897df0ee…b0c5
0x40c49f…2af0
4 touches
1 conflict
0xc5d7e85d…b578
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x33bd5ec4…af53
0xa6afd3…d132
4 touches
1 conflict
0xc7a15219…7745
0xa6afd3…d132
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: MarginAccount
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity