← previous blocknext block →recent activity
Analyzing
Block #80,313,842
18 transactions · 14 stateful · 2026-06-10 07:01:09 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,313,842 · 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
2w03w04w15w26w37w48w59w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000a
0x90c374…be45
12 touches
15 conflicts
0x00000000…000b
0x90c374…be45
12 touches
15 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x96d3f10e…4950
0x40c49f…2af0
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c0
0x1b6862…e19c
2 touches
0 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: 0x90c3747c…0ebe45
15 conflicts on slot 0x0000000000…00000a
Audit this contract →
← previous block·next block →recent activity