← previous blocknext block →recent activity
Analyzing
Block #80,166,286
40 transactions · 34 stateful · 2026-06-09 14:37:11 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
1.45
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #80,166,286 · 40 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w06w17w28w111w112w013w114w215w316w417w518w619w720w821w222w124w227w328w429w335w937w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
16 touches
28 conflicts
0xc38151f2…2bcb
0xc8689a…ee79
12 touches
15 conflicts
0x7895a98c…bbfa
0x34b655…2a6f
10 touches
10 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
10 touches
10 conflicts
0x908d4442…2c4b
0x34b655…2a6f
10 touches
10 conflicts
0xd8e48935…a5a9
0x34b655…2a6f
10 touches
10 conflicts
0x2495fdde…5ee9
0x34b655…2a6f
10 touches
10 conflicts
0xcdc8b4bb…7bce
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity