pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,457,915
← previous block
next block →
recent activity
Analyzing
Block #106,457,915
12 transactions · 10 stateful · 2026-09-20 12:01:42 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,457,915
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 1
#3
0xab083028
#4
updatePrices
#5
0x5acec890
#6
0x59558d29
#7
0x59558d29
#8
setData
#9
execFwdPositionOpsV2
#11
execOrders
#2
0xab083028
· blocks 1
#10
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x213ee207…a151
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9285
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9286
0x34ae4d…3fc5
2 touches
0 conflicts
0x2f74f175…9287
0x34ae4d…3fc5
2 touches
0 conflicts
0x3ba7edbb…80e6
0x34ae4d…3fc5
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: MarginAccount
1 conflict on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity