← previous blocknext block →recent activity
Analyzing
Block #81,481,917
22 transactions · 21 stateful · 2026-06-15 16:46:05 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #81,481,917 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w36w47w49w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x48acfd83…7ef0
0x40c49f…2af0
8 touches
6 conflicts
0x5581d709…ab77
0x2a68ba…90c5
6 touches
3 conflicts
0xc5d7e85d…b578
0x40c49f…2af0
4 touches
1 conflict
0xdc921364…4680
0x34b655…2a6f
4 touches
1 conflict
0x47ff2c0e…abcf
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
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: 0x40c49f17…d22af0
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity