← previous blocknext block →recent activity
Analyzing
Block #86,564,424
25 transactions · 20 stateful · 2026-07-09 05:54:49 UTC
Parallelism
72/100
Blocked
55%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,564,424 · 25 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
2w05w06w17w28w39w410w511w614w122w324w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x1eb1dd28…5f1b
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
8 touches
6 conflicts
0x96047c45…b64a
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity