pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,929,890
← previous block
next block →
recent activity
Analyzing
Block #105,929,890
13 transactions · 13 stateful · 2026-09-18 15:44:02 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#105,929,890
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
execOrders
#4
0x5acec890
#5
0x928e4afa
#6
0x59558d29
#7
execFwdPositionOpsV2
#8
0xed82b078
#9
transferWithAuthorization
· blocks 1
#11
setData
#12
execOrders
#2
0xab083028
#10
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x023277a7…72b5
0x34b655…2a6f
2 touches
0 conflicts
0x0a0d0bdf…5370
0x34b655…2a6f
2 touches
0 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
2 touches
0 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0x65e795ca…0320
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: MarginAccount
1 conflict on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity