← previous blocknext block →recent activity
Analyzing
Block #86,686,319
33 transactions · 30 stateful · 2026-07-09 19:31:31 UTC
Parallelism
64/100
Blocked
67%
Avg conflicts / tx
2.03
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #86,686,319 · 33 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w26w38w09w110w211w312w413w514w617w519w220w721w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x5d537073…cf27
0x34b655…2a6f
10 touches
10 conflicts
0x745a7fd6…5fea
0x34b655…2a6f
10 touches
10 conflicts
0xfc578b53…9b1f
0xa6afd3…d132
8 touches
6 conflicts
0x9da6e429…074d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x2b20b4d1…0321
0xd32edf…ff58
7 touches
6 conflicts
0x13a54fa2…5ae3
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity