← previous blocknext block →recent activity
Analyzing
Block #86,664,733
25 transactions · 24 stateful · 2026-07-09 17:07:24 UTC
Parallelism
68/100
Blocked
54%
Avg conflicts / tx
1.48
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,664,733 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w510w611w713w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x2d7ea048…d78e
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
14 touches
21 conflicts
0x70b87e4d…65d5
0x34b655…2a6f
14 touches
21 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
14 touches
21 conflicts
0x87f3dc22…eb64
0x34b655…2a6f
14 touches
21 conflicts
0xa3e06ffb…6c2b
0x34b655…2a6f
14 touches
21 conflicts
0xd786a4f1…12d6
0x34b655…2a6f
14 touches
21 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