← previous blocknext block →recent activity
Analyzing
Block #86,855,354
13 transactions · 10 stateful · 2026-07-10 14:20:50 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,855,354 · 13 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x06a0c880…707b
0x34b655…2a6f
2 touches
0 conflicts
0x0c57679c…99c9
0x34b655…2a6f
2 touches
0 conflicts
0x12205b11…edd1
0x34b655…2a6f
2 touches
0 conflicts
0x1d84bebc…07d0
0x34b655…2a6f
2 touches
0 conflicts
0x1d84bebc…07d1
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x216ffe6648…bf1f94
Audit this contract →
← previous block·next block →recent activity