pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,818,251
← previous block
next block →
recent activity
Analyzing
Block #86,818,251
9 transactions · 7 stateful · 2026-07-10 10:12:39 UTC
Parallelism
67
/100
Blocked
43
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,818,251
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
withdraw
#3
execFwdPositionOps
· blocks 2
#5
updateDataFeedsValuesPartial
#6
setData
#4
execFwdPositionOps
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x8d888c90…5479
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x0cbca242…3764
0x34b655…2a6f
2 touches
0 conflicts
0x145b9bbf…e50e
0x34b655…2a6f
2 touches
0 conflicts
0x145b9bbf…e50f
0x34b655…2a6f
2 touches
0 conflicts
0x1c029d35…305e
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
0x0000000000…0000c9
Audit this contract →
← previous block
·
next block →
recent activity