← previous blocknext block →recent activity
Analyzing
Block #80,248,422
22 transactions · 19 stateful · 2026-06-09 23:45:00 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,248,422 · 22 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
3w04w15w26w37w48w09w111w413w014w519w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x179fe783…6945
0xa6afd3…d132
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
8 touches
6 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
8 touches
6 conflicts
0x692de2da…5986
0x34b655…2a6f
8 touches
6 conflicts
0x40970e69…da50
0x69df8a…6292
8 touches
6 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
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