pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,878,905
← previous block
next block →
recent activity
Analyzing
Block #102,878,905
12 transactions · 10 stateful · 2026-09-07 23:00:10 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,878,905
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x3e2e8792
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0x59558d29
#5
execPerpOps
#6
execPerpOps
#8
transferWithAuthorization
· blocks 1
#10
setData
#11
setData
#7
execFwdPositionOpsV2
#9
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc8d572c…b27d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x23361cbc…b058
0x34b655…2a6f
2 touches
0 conflicts
0xa2042b9b…0ecb
0x34b655…2a6f
2 touches
0 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
2 touches
0 conflicts
0xca841faa…486a
0x34b655…2a6f
2 touches
0 conflicts
0xdd57cdb2…d3e9
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
0xfc8d572cb3…e5b27d
Audit this contract →
← previous block
·
next block →
recent activity