pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,376,811
← previous block
next block →
recent activity
Analyzing
Block #102,376,811
11 transactions · 11 stateful · 2026-09-06 04:41:30 UTC
Parallelism
73
/100
Blocked
27
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,376,811
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
executePacked
· blocks 2
#2
updatePrices
#5
0xab083028
#6
0x59558d29
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
· blocks 1
#10
setData
#3
0xab083028
· blocks 1
#9
execFwdPositionOpsV2
#4
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
4 touches
1 conflict
0x958294fe…2c10
0x34b655…2a6f
4 touches
1 conflict
0xa128bff8…25e5
0x34b655…2a6f
3 touches
1 conflict
0x12530975…a089
0x3bd359…433a
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x00000000…0000
0x453805…c7fd
2 touches
0 conflicts
0x00000000…0002
0x453805…c7fd
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
3 conflicts on slot
0xaad6be10ae…2c0801
Audit this contract →
← previous block
·
next block →
recent activity