← previous blocknext block →recent activity
Analyzing
Block #80,219,097
85 transactions · 68 stateful · 2026-06-09 20:29:26 UTC
Parallelism
80/100
Blocked
82%
Avg conflicts / tx
3.68
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #80,219,097 · 85 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w116w220w321w222w423w524w328w729w830w931w1064w1065w1166w1267w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
28 touches
91 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
22 touches
55 conflicts
0xc38151f2…2bcb
0xc8689a…ee79
18 touches
36 conflicts
0xd4c78744…3ef8
0xd32edf…ff58
17 touches
36 conflicts
0xcef70a96…db44
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x48a88f3d…7824
0x34b655…2a6f
16 touches
28 conflicts
0x080ec687…da80
0x34b655…2a6f
16 touches
28 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: Perpl
91 conflicts on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity