← previous blocknext block →recent activity
Analyzing
Block #86,746,860
38 transactions · 33 stateful · 2026-07-10 02:15:50 UTC
Parallelism
71/100
Blocked
70%
Avg conflicts / tx
2.11
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,746,860 · 38 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w48w59w010w111w212w327w429w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x4777ff21…5480
0xd32edf…ff58
11 touches
15 conflicts
0x66f473d3…2d03
0xa6afd3…d132
10 touches
10 conflicts
0x11998eac…f9a0
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 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