← previous blocknext block →recent activity
Analyzing
Block #86,837,639
14 transactions · 11 stateful · 2026-07-10 12:22:27 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,837,639 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf45f2405…c8f9
0x34b655…2a6f
4 touches
1 conflict
0xdfd1344f…43f5
0x34b655…2a6f
4 touches
1 conflict
0xea31bd73…9e9c
0x34b655…2a6f
4 touches
1 conflict
0xec2a8d79…70cb
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x254a2653…24ed
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
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
1 conflict on slot 0xf45f24056b…37c8f9
Audit this contract →
← previous block·next block →recent activity