pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,555,965
← previous block
next block →
recent activity
Analyzing
Block #95,555,965
9 transactions · 8 stateful · 2026-08-13 06:09:50 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,555,965
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
repayWithCollateral
#3
execFwdPositionOps
· blocks 1
#5
execOrders
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x59558d29
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x78b52df8…344b
0x34b655…2a6f
4 touches
1 conflict
0x7523c6af…ea66
0x34b655…2a6f
4 touches
1 conflict
0x43b81533…373d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xca713a22…3083
0x34b655…2a6f
4 touches
1 conflict
0x159cff26…7665
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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