pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,206,379
← previous block
next block →
recent activity
Analyzing
Block #102,206,379
13 transactions · 13 stateful · 2026-09-05 14:18:04 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
#102,206,379
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
approve
· blocks 1
#4
execOrders
· blocks 1
#6
0x59558d29
#7
setData
#8
execFwdPositionOpsV2
#9
execFwdPositionOpsV2
#10
execFwdPositionOpsV2
#11
0xed82b078
#12
execOrders
#3
swap
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xcfd82175…0b1a
0x284f45…7777
2 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4ce8693f…0340
0x284f45…7777
2 touches
0 conflicts
0x5b0621ee…3c2c
0x284f45…7777
2 touches
0 conflicts
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x1368c0ff…46af
0x34b655…2a6f
2 touches
0 conflicts
0x720ae293…6a10
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
0xbde524f475…b143bf
Audit this contract →
← previous block
·
next block →
recent activity