← previous blocknext block →recent activity
Analyzing
Block #86,910,813
11 transactions · 10 stateful · 2026-07-10 20:31:44 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,910,813 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xdea31a88…6cfe
0x34b655…2a6f
4 touches
1 conflict
0xdea31a88…6cff
0x34b655…2a6f
4 touches
1 conflict
0xe38c11ce…1afd
0x34b655…2a6f
4 touches
1 conflict
0x1515ea2e…b538
0x34b655…2a6f
4 touches
1 conflict
0x38b61269…48d7
0x34b655…2a6f
4 touches
1 conflict
0x3cf50d44…961b
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity