← previous blocknext block →recent activity
Analyzing
Block #86,820,154
18 transactions · 17 stateful · 2026-07-10 10:25:23 UTC
Parallelism
72/100
Blocked
53%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,820,154 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w17w210w111w212w313w415w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x1586ff62…0ebe
0x34b655…2a6f
4 touches
1 conflict
0x1586ff62…0ebf
0x34b655…2a6f
4 touches
1 conflict
0x19caa5cc…17c7
0x34b655…2a6f
4 touches
1 conflict
0x2fd12b6c…02cc
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity