← previous blocknext block →recent activity
Analyzing
Block #80,140,533
36 transactions · 28 stateful · 2026-06-09 11:45:30 UTC
Parallelism
72/100
Blocked
75%
Avg conflicts / tx
1.81
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #80,140,533 · 36 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w07w28w39w410w511w412w413w514w618w125w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xde6b917f…3a72
0xa6afd3…d132
10 touches
10 conflicts
0x4c04ce68…d007
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x82ded54c…06f6
0x34b655…2a6f
8 touches
6 conflicts
0x90f07a4f…d932
0x34b655…2a6f
8 touches
6 conflicts
0x1504aa7b…24ad
0xa6afd3…d132
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: Perpl
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity