← previous blocknext block →recent activity
Analyzing
Block #86,493,950
15 transactions · 14 stateful · 2026-07-08 22:03:25 UTC
Parallelism
53/100
Blocked
64%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,493,950 · 15 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
1w02w03w14w25w36w47w58w19w613w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
12 touches
15 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad07
0x34b655…2a6f
10 touches
10 conflicts
0x4203ff9b…38e2
0x34b655…2a6f
10 touches
10 conflicts
0x6286953c…1cdf
0x34b655…2a6f
10 touches
10 conflicts
0x98d58911…19f2
0x34b655…2a6f
10 touches
10 conflicts
0x326a02b5…8dad
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
15 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity