← previous blocknext block →recent activity
Analyzing
Block #86,759,140
19 transactions · 17 stateful · 2026-07-10 03:37:51 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,759,140 · 19 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
6w07w110w011w112w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ba89834…1826
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a59
0x34b655…2a6f
4 touches
1 conflict
0x7d7ed9e4…4a5a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x846048e8…98f6
0x34b655…2a6f
4 touches
1 conflict
0x8eedf936…a0c3
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xadd2210b…9e29
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 0x6ba8983443…5c1826
Audit this contract →
← previous block·next block →recent activity