← previous blocknext block →recent activity
Analyzing
Block #86,623,864
48 transactions · 33 stateful · 2026-07-09 12:33:07 UTC
Parallelism
69/100
Blocked
73%
Avg conflicts / tx
1.81
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,623,864 · 48 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w110w011w012w113w214w315w416w517w618w719w820w121w524w125w226w328w436w1245w246w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xa29182a1…c12c
0x34b655…2a6f
10 touches
10 conflicts
0xe6805ef8…e22e
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xfb4cb196…8c4a
0x34b655…2a6f
8 touches
6 conflicts
0x226b4d09…8113
0x34b655…2a6f
6 touches
3 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity