← previous blocknext block →recent activity
Analyzing
Block #80,820,712
27 transactions · 22 stateful · 2026-06-12 15:21:05 UTC
Parallelism
85/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,820,712 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w06w07w111w112w013w114w015w217w118w023w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00ddbbf2…4588
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x623af2c1…5034
0x34b655…2a6f
4 touches
1 conflict
0x8eef368f…aa21
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x936f37a8…9812
0xa6afd3…d132
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
3 conflicts on slot 0x00ddbbf292…ff4588
Audit this contract →
← previous block·next block →recent activity