← previous blocknext block →recent activity
Analyzing
Block #86,634,317
53 transactions · 33 stateful · 2026-07-09 13:42:59 UTC
Parallelism
75/100
Blocked
73%
Avg conflicts / tx
1.64
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #86,634,317 · 53 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w39w410w511w612w440w441w542w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xcd11fb6b…ab8d
0xd32edf…ff58
13 touches
21 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xb43dc900…22f2
0xa6afd3…d132
10 touches
10 conflicts
0xda46a376…f6a6
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x91945265…e592
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity