← previous blocknext block →recent activity
Analyzing
Block #86,820,502
40 transactions · 31 stateful · 2026-07-10 10:27:44 UTC
Parallelism
77/100
Blocked
68%
Avg conflicts / tx
1.32
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,820,502 · 40 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w38w49w010w111w212w313w014w117w219w331w532w633w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x4b20a3bb…ee21
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0x17c44db3…8888
0xa6afd3…d132
8 touches
6 conflicts
0xbcc5ae85…6ba2
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity