pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,759,965
← previous block
next block →
recent activity
Analyzing
Block #85,759,965
12 transactions · 10 stateful · 2026-07-05 12:24:39 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,759,965
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
execPerpOps
#5
execFwdPositionOps
· blocks 1
#6
0x3f5c179b
#7
forward
#9
setData
#10
0x876507…ed30
#11
execOrders
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5af10b50…8d5c
0x34b655…2a6f
4 touches
1 conflict
0xa3ba46d3…98d7
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5eb
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f9
0x34b655…2a6f
4 touches
1 conflict
0xe63a43f9…6583
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x26212add…d2f6
0x34b655…2a6f
4 touches
1 conflict
0xc493882e…2cef
0x065c9d…c394
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
0x5af10b50aa…348d5c
Audit this contract →
← previous block
·
next block →
recent activity