← previous blocknext block →recent activity
Analyzing
Block #80,465,832
21 transactions · 19 stateful · 2026-06-10 23:53:57 UTC
Parallelism
76/100
Blocked
63%
Avg conflicts / tx
1.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,465,832 · 21 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
1w02w13w04w15w26w17w18w29w315w416w017w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
8 touches
6 conflicts
0xe4afaa2f…3b69
0xa6afd3…d132
8 touches
6 conflicts
0x3d34f2bd…5d63
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity