pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,145,939
← previous block
next block →
recent activity
Analyzing
Block #96,145,939
10 transactions · 9 stateful · 2026-08-15 07:38:50 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,145,939
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execOrder
· blocks 1
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#8
0x3f5c179b
#9
setData
#3
execOrder
· blocks 1
#4
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x00e21a9f…3583
0x34b655…2a6f
2 touches
0 conflicts
0x16e06a6b…4395
0x34b655…2a6f
2 touches
0 conflicts
0x40be70d4…6722
0x34b655…2a6f
2 touches
0 conflicts
0x424934c8…f2f1
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
0xf5ea108a6a…e5dbf6
Audit this contract →
← previous block
·
next block →
recent activity