pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,318,350
← previous block
next block →
recent activity
Analyzing
Block #96,318,350
12 transactions · 12 stateful · 2026-08-15 22:06:00 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,318,350
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
repayWithCollateral
#9
0x94defb17
· blocks 1
#11
setData
#10
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f1bb850…546d
0x968279…9342
4 touches
1 conflict
0x9f1bb850…546f
0x968279…9342
4 touches
1 conflict
0xd5f3026c…9423
0x968279…9342
4 touches
1 conflict
0xd5f3026c…9424
0x968279…9342
4 touches
1 conflict
0xd5f3026c…9427
0x968279…9342
4 touches
1 conflict
0xd5f3026c…9428
0x968279…9342
4 touches
1 conflict
0xd5f3026c…9429
0x968279…9342
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
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:
0x96827978…f09342
1 conflict on slot
0x9f1bb8506f…d4546d
Audit this contract →
← previous block
·
next block →
recent activity