← previous blocknext block →recent activity
Analyzing
Block #86,930,166
13 transactions · 11 stateful · 2026-07-10 22:40:59 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,930,166 · 13 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
2w06w17w28w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9369a89…39a2
0x34b655…2a6f
4 touches
1 conflict
0xb9369a89…39a3
0x34b655…2a6f
4 touches
1 conflict
0xefda3300…69b0
0x34b655…2a6f
4 touches
1 conflict
0xf9e23360…8ef7
0x34b655…2a6f
4 touches
1 conflict
0xffcb5f20…df5a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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
1 conflict on slot 0xb9369a8906…b239a2
Audit this contract →
← previous block·next block →recent activity