pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,035,826
← previous block
next block →
recent activity
Analyzing
Block #106,035,826
14 transactions · 11 stateful · 2026-09-19 00:37:22 UTC
Parallelism
86
/100
Blocked
18
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,035,826
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updatePrices
#3
0xab083028
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x59558d29
· blocks 1
#7
0x59558d29
#8
setData
#9
handleOps
#11
0x6aadd945
#12
exactInputSingle
#13
execOrders
#6
0x59558d29
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1f2de38a…5120
0x065c9d…c394
2 touches
0 conflicts
0x22041ec1…c786
0x065c9d…c394
2 touches
0 conflicts
0x8b879963…7fb0
0x065c9d…c394
2 touches
0 conflicts
0xabcbe66d…dc3c
0x065c9d…c394
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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