pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,402,899
← previous block
next block →
recent activity
Analyzing
Block #106,402,899
13 transactions · 12 stateful · 2026-09-20 07:24:46 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,402,899
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
0x5acec890
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#8
batchUpdate
#10
0x6aaf8a41
#11
0x61d59c2d
#12
execOrders
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x58722c60…a81a
0x34b655…2a6f
2 touches
0 conflicts
0x6c32b694…d019
0x34b655…2a6f
2 touches
0 conflicts
0x80398c66…f3cc
0x34b655…2a6f
2 touches
0 conflicts
0xca841faa…486a
0x34b655…2a6f
2 touches
0 conflicts
0xe5c478d0…2409
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity