pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,212,952
← previous block
next block →
recent activity
Analyzing
Block #103,212,952
11 transactions · 11 stateful · 2026-09-09 03:03:22 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#103,212,952
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updatePrices
#3
0x6ad2e98b
· blocks 1
#5
0xab083028
#6
updateDataFeedsValuesPartial
#7
0x59558d29
#8
setData
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#4
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ec07cf7…c0c9
0x34b655…2a6f
2 touches
0 conflicts
0x0f763490…ff64
0x34b655…2a6f
2 touches
0 conflicts
0x0ffac39e…6d34
0x34b655…2a6f
2 touches
0 conflicts
0x102a6e48…23a1
0x34b655…2a6f
2 touches
0 conflicts
0x16d79cd9…2a9c
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