← previous blocknext block →recent activity
Analyzing
Block #80,703,788
21 transactions · 21 stateful · 2026-06-12 02:21:20 UTC
Parallelism
57/100
Blocked
57%
Avg conflicts / tx
2.05
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #80,703,788 · 21 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0xa82908…7f0f
18 touches
36 conflicts
0x87bfeaf6…fe1f
0x2c9575…7777
18 touches
36 conflicts
0xd4d4211d…b9ff
0x3bd359…433a
18 touches
36 conflicts
0x00000000…0000
0xa82908…7f0f
18 touches
36 conflicts
0x00000000…0001
0xa82908…7f0f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe99ebc4d…22f9
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: 0xa82908ee…757f0f
36 conflicts on slot 0x0000000000…000003
Audit this contract →
← previous block·next block →recent activity