← previous blocknext block →recent activity
Analyzing
Block #80,246,810
33 transactions · 26 stateful · 2026-06-09 23:34:15 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,246,810 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w07w18w29w310w111w216w017w118w220w423w430w031w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x179fe783…6945
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x794b8f81…3eae
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 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