pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,129,065
← previous block
next block →
recent activity
Analyzing
Block #96,129,065
12 transactions · 10 stateful · 2026-08-15 06:13:56 UTC
Parallelism
83
/100
Blocked
30
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,129,065
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xd60faa87
· blocks 1
#2
updatePrices
#3
0xab083028
#4
0x5acec890
· blocks 1
#6
updateDataFeedsValuesPartial
#8
setData
#9
setData
#10
execFwdPositionOpsV2
· blocks 1
#5
execOrders
#7
dagSwapByOrderId
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
7
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85915bad…0463
0x834d94…8555
4 touches
1 conflict
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0x00000000…0005
0x834d94…8555
4 touches
1 conflict
0x85915bad…0461
0x834d94…8555
4 touches
1 conflict
0x85915bad…0462
0x834d94…8555
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0x16f2b4e1…e98b
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:
0x834d94a0…2e8555
1 conflict on slot
0x85915bad08…5b0463
Audit this contract →
← previous block
·
next block →
recent activity