← previous blocknext block →recent activity
Analyzing
Block #86,564,638
18 transactions · 15 stateful · 2026-07-09 05:56:15 UTC
Parallelism
50/100
Blocked
53%
Avg conflicts / tx
1.78
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,564,638 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w410w511w612w713w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x922c7ebd…6600
0xc8689a…ee79
10 touches
10 conflicts
0x924bac95…3f39
0x34b655…2a6f
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
10 touches
10 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
10 touches
10 conflicts
0xe727ab72…768b
0x34b655…2a6f
10 touches
10 conflicts
0xe7e35792…f959
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity