← previous blocknext block →recent activity
Analyzing
Block #81,407,210
18 transactions · 16 stateful · 2026-06-15 08:28:11 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,407,210 · 18 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
1w02w03w14w06w27w19w310w411w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x897df0ee…b0c5
0x40c49f…2af0
8 touches
6 conflicts
0x5581d709…ab77
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xc5d7e85d…b578
0x40c49f…2af0
6 touches
3 conflicts
0x6e733b13…b909
0x851145…3f07
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xc7f84cd8…0acd
0x40c49f…2af0
3 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
6 conflicts on slot 0x897df0ee4f…0cb0c5
Audit this contract →
← previous block·next block →recent activity