pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,247,600
← previous block
next block →
recent activity
Analyzing
Block #102,247,600
13 transactions · 12 stateful · 2026-09-05 17:46:50 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,247,600
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
transfer
#3
0xab083028
#4
0x3e2e8792
#5
0x59558d29
#6
executeBatch
· blocks 1
#8
setData
#9
redeemDelegations
#10
forward
#11
execFwdPositionOpsV2
· blocks 1
#7
executeBatch
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22659874…ec0b
0x34b655…2a6f
4 touches
1 conflict
0xe188ad90…d23f
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xbd590df7…9891
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x6d762554…bd7a
0x34b655…2a6f
2 touches
0 conflicts
0xb2560305…f27d
0x34b655…2a6f
2 touches
0 conflicts
0xc025c322…37af
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:
Perpl
1 conflict on slot
0x22659874e8…54ec0b
Audit this contract →
← previous block
·
next block →
recent activity