← previous blocknext block →recent activity
Analyzing
Block #86,632,378
48 transactions · 40 stateful · 2026-07-09 13:30:02 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
1.9
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #86,632,378 · 48 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w28w39w413w014w115w216w317w418w519w620w721w822w929w431w534w336w237w538w542w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
20 touches
45 conflicts
0x9365e097…ff56
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
10 touches
10 conflicts
0x727fbce7…0c80
0x34b655…2a6f
8 touches
6 conflicts
0x8eb0ac6b…a73a
0x34b655…2a6f
8 touches
6 conflicts
0xbde30d77…b032
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
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
45 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity