← previous blocknext block →recent activity
Analyzing
Block #86,836,789
18 transactions · 14 stateful · 2026-07-10 12:16:46 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,836,789 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w38w09w111w012w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x8d888c90…5479
0x34b655…2a6f
6 touches
3 conflicts
0x0c15f714…46ab
0x34b655…2a6f
4 touches
1 conflict
0x135cdc1d…7b2f
0x34b655…2a6f
4 touches
1 conflict
0x53b1efb4…c65d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity