pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,216,085
← previous block
next block →
recent activity
Analyzing
Block #103,216,085
18 transactions · 18 stateful · 2026-09-09 03:19:08 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#103,216,085
· 18 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
#3
execOrder
#4
execOrder
#5
0x5acec890
#6
0x5acec890
#7
0x5acec890
#8
0x5acec890
#9
0x928e4afa
#10
0x5acec890
#11
0x5acec890
#12
0x59558d29
#13
execFwdPositionOpsV2
#14
setData
#15
0x6aa0d030
#16
0x61d59c2d
#17
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x34ae4d…3fc5
2 touches
0 conflicts
0x48ed1159…abe9
0x34ae4d…3fc5
2 touches
0 conflicts
0x0a2131b3…455e
0x34b655…2a6f
2 touches
0 conflicts
0x287ab03c…1d20
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.
← previous block
·
next block →
recent activity