pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,693,708
← previous block
next block →
recent activity
Analyzing
Block #96,693,708
11 transactions · 8 stateful · 2026-08-17 05:34:10 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,693,708
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb414539a
#2
0x5acec890
· blocks 1
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
execOrders
#6
execOrders
#8
0x0c7abd22
#9
execFwdPositionOpsV2
#10
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x79e5e792…dfe6
0x11ed3b…2c96
2 touches
0 conflicts
0x982ba7f1…e834
0x11ed3b…2c96
2 touches
0 conflicts
0x96a76165…f807
0x21e325…7777
2 touches
0 conflicts
0xbc467e7a…af36
0x21e325…7777
2 touches
0 conflicts
0x99bd7b88…4427
0x350035…7777
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
0xea02471df2…601542
Audit this contract →
← previous block
·
next block →
recent activity