← previous blocknext block →recent activity
Analyzing
Block #80,271,269
32 transactions · 25 stateful · 2026-06-10 02:17:17 UTC
Parallelism
88/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,271,269 · 32 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
1w02w13w24w38w09w111w012w117w018w121w022w127w028w129w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x7a42c328…8875
0xd32edf…ff58
7 touches
6 conflicts
0x6d94d7d6…6ed4
0x34b655…2a6f
6 touches
3 conflicts
0x84fb2a36…db89
0x34b655…2a6f
6 touches
3 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
6 touches
3 conflicts
0xb138d087…4689
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…006f
0x1efe02…37d6
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