← previous blocknext block →recent activity
Analyzing
Block #80,163,434
20 transactions · 13 stateful · 2026-06-09 14:18:09 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,163,434 · 20 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
5w06w014w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0x59645a97…3ca1
0x34b655…2a6f
6 touches
3 conflicts
0x66812b79…4c80
0x34b655…2a6f
6 touches
3 conflicts
0x81e1f4e8…08d7
0x34b655…2a6f
6 touches
3 conflicts
0x8fbde2b3…9b8f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xce7c598a…631b
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity