pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,436,904
← previous block
next block →
recent activity
Analyzing
Block #96,436,904
11 transactions · 11 stateful · 2026-08-16 08:02:14 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,436,904
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
0x45b7e41f
#3
0x5acec890
#4
0x5acec890
#5
execFwdPositionOpsV2
· blocks 1
#7
updateDataFeedsValuesPartial
#8
updatePosition
#9
execFwdPositionOpsV2
#10
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x74e0d9d2…47d7
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xa00ea7ab…4cea
0x34b655…2a6f
4 touches
1 conflict
0xa7481e1f…531f
0x34b655…2a6f
4 touches
1 conflict
0x1f94aad9…7ce0
0x34b655…2a6f
2 touches
0 conflicts
0x3c78ca04…432c
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
0x0000000000…0000c9
Audit this contract →
← previous block
·
next block →
recent activity