pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,038,745
← previous block
next block →
recent activity
Analyzing
Block #96,038,745
10 transactions · 10 stateful · 2026-08-14 22:39:39 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,038,745
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
execOrders
#3
transfer
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
· blocks 1
#7
setData
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc0ce381…a6cf
0x34b655…2a6f
4 touches
1 conflict
0x344bc09a…942f
0x34b655…2a6f
4 touches
1 conflict
0x714144d3…8396
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x931bd7a5…b6b9
0x34b655…2a6f
4 touches
1 conflict
0xd4702f73…926c
0x34b655…2a6f
4 touches
1 conflict
0xd6289e73…4276
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 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
0xdc0ce381a9…daa6cf
Audit this contract →
← previous block
·
next block →
recent activity