← previous blocknext block →recent activity
Analyzing
Block #86,811,689
23 transactions · 19 stateful · 2026-07-10 09:28:47 UTC
Parallelism
91/100
Blocked
11%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,811,689 · 23 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
1w04w06w19w012w013w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe22ab637…7a8e
0x34b655…2a6f
4 touches
1 conflict
0xff2c099b…0b09
0x34b655…2a6f
4 touches
1 conflict
0xf273c816…7561
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf273c816…7560
0x34b655…2a6f
4 touches
1 conflict
0x2f4b1dc8…e9fa
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0xe22ab637d9…007a8e
Audit this contract →
← previous block·next block →recent activity