pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,717,899
← previous block
next block →
recent activity
Analyzing
Block #95,717,899
14 transactions · 14 stateful · 2026-08-13 19:45:23 UTC
Parallelism
86
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,717,899
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
transfer
#4
0x5acec890
#5
updatePrices
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
0x3f5c179b
#9
0x94defb17
· blocks 1
#11
0x6a7e1f4b
#12
setData
#13
execOrders
#2
0xab083028
#10
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x948ac30b…77ba
0x968279…9342
4 touches
1 conflict
0x00000000…0006
0x968279…9342
4 touches
1 conflict
0x1b376992…0221
0x968279…9342
4 touches
1 conflict
0x1b376992…0222
0x968279…9342
4 touches
1 conflict
0x1b376992…0225
0x968279…9342
4 touches
1 conflict
0x1b376992…0226
0x968279…9342
4 touches
1 conflict
0x1b376992…0228
0x968279…9342
4 touches
1 conflict
0x948ac30b…77b7
0x968279…9342
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
0x948ac30bc5…8877ba
Audit this contract →
← previous block
·
next block →
recent activity