← previous blocknext block →recent activity
Analyzing
Block #86,857,037
44 transactions · 35 stateful · 2026-07-10 14:32:04 UTC
Parallelism
59/100
Blocked
77%
Avg conflicts / tx
3.14
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,857,037 · 44 txs across 18 waves · depth 18
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
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w27w38w010w116w017w118w219w320w421w522w623w724w425w826w927w1032w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x1941b441…5889
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xa583444d…b85e
0xd32edf…ff58
11 touches
15 conflicts
0x85440df6…832c
0x34b655…2a6f
10 touches
10 conflicts
0x9c5d843b…4d44
0x34b655…2a6f
10 touches
10 conflicts
0x2a89f1bc…0e69
0x34b655…2a6f
10 touches
10 conflicts
0x2e4e7336…e906
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity