← previous blocknext block →recent activity
Analyzing
Block #80,124,133
26 transactions · 20 stateful · 2026-06-09 09:56:15 UTC
Parallelism
77/100
Blocked
60%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,124,133 · 26 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
1w02w13w25w26w37w48w312w013w114w220w221w322w423w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0xcdc8b4bb…7bce
0x34b655…2a6f
6 touches
3 conflicts
0x67b7f565…0017
0x34b655…2a6f
6 touches
3 conflicts
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x99cc5a4c…28e7
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity