pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,329,121
← previous block
next block →
recent activity
Analyzing
Block #102,329,121
11 transactions · 11 stateful · 2026-09-06 00:39:57 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,329,121
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#3
0x59558d29
#4
updateDataFeedsValuesPartial
#5
poke
#6
setData
#7
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
#10
execOrders
#2
0x3e2e8792
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x232b0b19…d946
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xc1584d04…37d4
0x34b655…2a6f
4 touches
1 conflict
0x347abf57…4b86
0x34b655…2a6f
2 touches
0 conflicts
0x3643741b…109c
0x34b655…2a6f
2 touches
0 conflicts
0x45885570…ed97
0x34b655…2a6f
2 touches
0 conflicts
0x53b4ef2b…8a05
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity