← previous blocknext block →recent activity
Analyzing
Block #86,903,823
12 transactions · 10 stateful · 2026-07-10 19:44:58 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,903,823 · 12 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7548b289…f0dc
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xed4a0d72…065f
0x34b655…2a6f
4 touches
1 conflict
0xff32c1c4…3092
0x34b655…2a6f
4 touches
1 conflict
0x1b89bfcf…8506
0x34b655…2a6f
4 touches
1 conflict
0x1b89bfcf…8505
0x34b655…2a6f
4 touches
1 conflict
0x6bc63e94…ec4f
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
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 0x7548b289b6…abf0dc
Audit this contract →
← previous block·next block →recent activity