pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,121,340
← previous block
next block →
recent activity
Analyzing
Block #96,121,340
11 transactions · 11 stateful · 2026-08-15 05:35:03 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,121,340
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#3
0x5acec890
#4
dagSwapByOrderId
#5
updateDataFeedsValuesPartial
#6
0x222d4ad6
#7
execFwdPositionOpsV2
· blocks 1
#9
setData
#10
execOrders
#2
0x5acec890
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x6aa6fbd5…0c77
0x34b655…2a6f
4 touches
1 conflict
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x2015205e…6b1d
0x34b655…2a6f
2 touches
0 conflicts
0x78860c4f…cade
0x34b655…2a6f
2 touches
0 conflicts
0x85825765…7af0
0x34b655…2a6f
2 touches
0 conflicts
0xa2e89145…7dfa
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
0xc824469a90…af641d
Audit this contract →
← previous block
·
next block →
recent activity