← previous blocknext block →recent activity
Analyzing
Block #86,821,103
14 transactions · 12 stateful · 2026-07-10 10:31:50 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,821,103 · 14 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
2w06w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cc1393f…07fb
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe9898547…a77f
0x34b655…2a6f
4 touches
1 conflict
0x21de4cce…a3e9
0x34b655…2a6f
4 touches
1 conflict
0x3230413b…bc7f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b30a6e6…b249
0x34b655…2a6f
4 touches
1 conflict
0x7dc98782…f193
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
3 conflicts on slot 0x8cc1393fcb…7307fb
Audit this contract →
← previous block·next block →recent activity