pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,121,083
← previous block
next block →
recent activity
Analyzing
Block #96,121,083
11 transactions · 9 stateful · 2026-08-15 05:33:45 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,121,083
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeabbe9d8
· blocks 1
#2
updateDataFeedsValuesPartial
#3
execPerpOps
#4
execPerpOps
#5
0x5acec890
#6
execOrders
#8
execFwdPositionOpsV2
· blocks 1
#10
setData
#7
dagSwapByOrderId
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0x834d94…8555
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0x00000000…0005
0x834d94…8555
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0xa060b594…669d
0x754704…b603
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x39c2102b…cc0d
0x754704…b603
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:
0x834d94a0…2e8555
1 conflict on slot
0x0000000000…000003
Audit this contract →
← previous block
·
next block →
recent activity