← previous blocknext block →recent activity
Analyzing
Block #86,564,102
19 transactions · 13 stateful · 2026-07-09 05:52:39 UTC
Parallelism
63/100
Blocked
62%
Avg conflicts / tx
1.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,564,102 · 19 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
3w04w15w26w37w48w59w617w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
12 touches
15 conflicts
0xdbf50b38…ac8c
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xf726e2e2…e561
0x34b655…2a6f
8 touches
6 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
8 touches
6 conflicts
0x1e48811e…2e39
0x34b655…2a6f
8 touches
6 conflicts
0xa5ab7b8a…c97b
0x34b655…2a6f
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity