← previous blocknext block →recent activity
Analyzing
Block #86,814,479
34 transactions · 33 stateful · 2026-07-10 09:47:25 UTC
Parallelism
71/100
Blocked
70%
Avg conflicts / tx
1.94
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,814,479 · 34 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w19w010w111w212w313w414w515w619w523w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x8f4206ee…1062
0xd32edf…ff58
11 touches
15 conflicts
0x8d888c90…5479
0x34b655…2a6f
10 touches
10 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
8 touches
6 conflicts
0xc9eaeefd…d5a3
0x34b655…2a6f
8 touches
6 conflicts
0x17a7f697…dcb4
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x046a928e…0012
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity