← previous blocknext block →recent activity
Analyzing
Block #80,652,942
28 transactions · 19 stateful · 2026-06-11 20:42:30 UTC
Parallelism
82/100
Blocked
53%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,652,942 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w08w117w018w119w220w023w124w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5c085c33…f4dd
0xd32edf…ff58
7 touches
6 conflicts
0xeef70cb9…5de7
0xea1b8e…c5ec
6 touches
3 conflicts
0x7b3f8378…b37d
0x34b655…2a6f
6 touches
3 conflicts
0xb138d087…4689
0x34b655…2a6f
6 touches
3 conflicts
0xc166a323…1f33
0x34b655…2a6f
6 touches
3 conflicts
0xd6de93a8…9382
0x34b655…2a6f
6 touches
3 conflicts
0x455b104f…3960
0xea1b8e…c5ec
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity