pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,073,121
← previous block
next block →
recent activity
Analyzing
Block #95,073,121
12 transactions · 11 stateful · 2026-08-11 13:27:35 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
#95,073,121
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x3f5c179b
#7
0x6df9e92b
#8
transfer
#9
setData
#10
0x59558d29
#11
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x092b7171…c16d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2840c278…bbc7
0x34b655…2a6f
2 touches
0 conflicts
0x2cfd3c31…ac31
0x34b655…2a6f
2 touches
0 conflicts
0x32a5ba7a…0b7a
0x34b655…2a6f
2 touches
0 conflicts
0x4092a8fb…7847
0x34b655…2a6f
2 touches
0 conflicts
0x43fd3667…094b
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
0x092b7171a3…96c16d
Audit this contract →
← previous block
·
next block →
recent activity