pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,107,986
← previous block
next block →
recent activity
Analyzing
Block #102,107,986
14 transactions · 14 stateful · 2026-09-05 05:59:21 UTC
Parallelism
86
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,107,986
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x693c2be6
#2
0xab083028
#3
0xab083028
#4
updatePrices
#5
0x5acec890
#6
0x5acec890
#7
0x928e4afa
#8
0x59558d29
#9
setData
#10
execFwdPositionOpsV2
· blocks 1
#12
0x6a9bafbc
#13
execOrders
#11
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ecf942d…fdb7
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ef74796…cd18
0x0a3323…0a3c
2 touches
0 conflicts
0xd5f4e613…6ca9
0x0a3323…0a3c
2 touches
0 conflicts
0x00000000…0010
0x2358b9…5037
2 touches
0 conflicts
0x915ce213…4c99
0x2358b9…5037
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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
0x9ecf942d43…97fdb7
Audit this contract →
← previous block
·
next block →
recent activity