← previous blocknext block →recent activity
Analyzing
Block #80,266,513
28 transactions · 23 stateful · 2026-06-10 01:45:38 UTC
Parallelism
79/100
Blocked
61%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,266,513 · 28 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
1w02w03w14w05w07w18w29w310w411w314w015w116w017w121w523w124w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x179fe783…6945
0xa6afd3…d132
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xa973fa68…f94d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xac79a0c7…be0f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 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: 0xa6afd386…b0d132
10 conflicts on slot 0x179fe7837f…326945
Audit this contract →
← previous block·next block →recent activity