← previous blocknext block →recent activity
Analyzing
Block #80,233,034
27 transactions · 21 stateful · 2026-06-09 22:02:26 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
1.07
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,233,034 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w29w010w111w314w321w222w323w424w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1e4de02…07e9
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xbaff104b…3edb
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xe755b8b7…72bf
0xd32edf…ff58
7 touches
6 conflicts
0xd6071d1d…496d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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 0xd1e4de026f…2607e9
Audit this contract →
← previous block·next block →recent activity