pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,529,468
← previous block
next block →
recent activity
Analyzing
Block #95,529,468
11 transactions · 9 stateful · 2026-08-13 03:56:33 UTC
Parallelism
73
/100
Blocked
33
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,529,468
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5acec890
· blocks 2
#3
updateDataFeedsValuesPartial
#4
0x222d4ad6
#5
0x3f5c179b
#7
forward
#9
setData
#6
execFwdPositionOps
· blocks 1
#10
execOrders
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
8
w2
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb754a75b…7cb9
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x03829ec3…d1be
0x34b655…2a6f
4 touches
1 conflict
0x14df0a67…26be
0x34b655…2a6f
2 touches
0 conflicts
0x224d6800…4508
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2685d38f…e3e8
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
0xac2a02739b…81721b
Audit this contract →
← previous block
·
next block →
recent activity