← previous blocknext block →recent activity
Analyzing
Block #86,848,072
25 transactions · 18 stateful · 2026-07-10 13:32:07 UTC
Parallelism
72/100
Blocked
39%
Avg conflicts / tx
0.56
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,848,072 · 25 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
12w013w014w115w119w220w321w422w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x119694b6…b8dc
0x34b655…2a6f
6 touches
3 conflicts
0x15489204…b558
0x34b655…2a6f
4 touches
1 conflict
0x25191452…d2ed
0x34b655…2a6f
4 touches
1 conflict
0x25db999f…f707
0x34b655…2a6f
4 touches
1 conflict
0x2c192519…3e3b
0x34b655…2a6f
4 touches
1 conflict
0x3ad67710…9613
0x34b655…2a6f
4 touches
1 conflict
0x3c190da8…2a1b
0x34b655…2a6f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity