← previous blocknext block →recent activity
Analyzing
Block #86,695,162
19 transactions · 18 stateful · 2026-07-09 20:30:28 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,695,162 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w414w015w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf58f4849…c7c7
0x34b655…2a6f
10 touches
10 conflicts
0x7eb0d4dc…f005
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x12573732…e891
0x34b655…2a6f
10 touches
10 conflicts
0x719fa25b…1814
0x34b655…2a6f
8 touches
6 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
8 touches
6 conflicts
0x976795c2…d0ce
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
10 conflicts on slot 0xf58f4849d1…77c7c7
Audit this contract →
← previous block·next block →recent activity