← previous blocknext block →recent activity
Analyzing
Block #80,380,889
24 transactions · 19 stateful · 2026-06-10 14:27:54 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,380,889 · 24 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
4w05w06w07w19w011w112w113w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xbaff104b…3edb
0xa6afd3…d132
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcb89a818…e7c1
0x34b655…2a6f
4 touches
1 conflict
0xd1e4de02…07e9
0x34b655…2a6f
4 touches
1 conflict
0xdba422af…42ec
0x34b655…2a6f
4 touches
1 conflict
0x9cf5ac50…1be9
0xa6afd3…d132
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
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: Perpl
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity