pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,185,819
← previous block
next block →
recent activity
Analyzing
Block #106,185,819
18 transactions · 16 stateful · 2026-09-19 13:12:13 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,185,819
· 18 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
0x5acec890
#4
0x5acec890
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
sweepNative
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
#16
execOrders
#17
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x3d338186…d4db
0x34b655…2a6f
2 touches
0 conflicts
0x4786839b…c29a
0x34b655…2a6f
2 touches
0 conflicts
0x4f4e6de0…68d1
0x34b655…2a6f
2 touches
0 conflicts
0x53c9cbb3…bdab
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.
← previous block
·
next block →
recent activity