pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,612,874
← previous block
next block →
recent activity
Analyzing
Block #96,612,874
9 transactions · 8 stateful · 2026-08-16 22:47:37 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,612,874
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execOrder
· blocks 1
#3
execFwdPositionOpsV2
· blocks 1
#4
execFwdPositionOpsV2
#5
updateDataFeedsValuesPartial
#7
setData
#8
execOrders
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76d36fa4…aaf6
0x34b655…2a6f
4 touches
1 conflict
0x93f1d5e2…928f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xda46a376…f6a6
0x34b655…2a6f
4 touches
1 conflict
0xe5a9274d…78d7
0x34b655…2a6f
4 touches
1 conflict
0x18978822…2623
0x34b655…2a6f
4 touches
1 conflict
0x42c0a5d3…a476
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
0x76d36fa4cb…8faaf6
Audit this contract →
← previous block
·
next block →
recent activity