pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,982,646
← previous block
next block →
recent activity
Analyzing
Block #91,982,646
12 transactions · 11 stateful · 2026-07-31 18:03:38 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,982,646
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
harvestMultiple
#4
updatePosition
#5
0x3f5c179b
#6
execFwdPositionOps
#7
cancelPendingOrder
#8
execOrders
#9
setData
#10
execOrders
#11
0x59558d29
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf15e2bf…d7a9
0x34b655…2a6f
4 touches
1 conflict
0x5a65207b…4f30
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9e04a514…7824
0x34b655…2a6f
4 touches
1 conflict
0x0626b624…3abe
0x34b655…2a6f
3 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
0xdf15e2bfed…35d7a9
Audit this contract →
← previous block
·
next block →
recent activity