← previous blocknext block →recent activity
Analyzing
Block #86,827,866
10 transactions · 9 stateful · 2026-07-10 11:17:07 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,827,866 · 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
3w04w05w16w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f4cddfd…3085
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x41f1e2e5…2edf
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe8adf936…34b2
0x188d58…ea8e
2 touches
0 conflicts
0xe8adf936…34b3
0x188d58…ea8e
2 touches
0 conflicts
0xfca291cb…c002
0x188d58…ea8e
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 0x0f4cddfd7a…203085
Audit this contract →
← previous block·next block →recent activity