← previous blocknext block →recent activity
Analyzing
Block #86,908,964
10 transactions · 9 stateful · 2026-07-10 20:19:23 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,908,964 · 10 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x8f7038d3…3804
0x34b655…2a6f
2 touches
0 conflicts
0xe4b8f2c5…f54d
0x34b655…2a6f
2 touches
0 conflicts
0xf66a16ae…0da8
0x34b655…2a6f
2 touches
0 conflicts
0xf6971361…0e3e
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0x07d8b1e8f0…0978c6
Audit this contract →
← previous block·next block →recent activity