pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,019,115
← previous block
next block →
recent activity
Analyzing
Block #102,019,115
13 transactions · 11 stateful · 2026-09-04 22:28:48 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,019,115
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf47a8bb
#2
approve
#3
matchOrders
#4
0x5acec890
· blocks 1
#5
0xab083028
#6
updateDataFeedsValuesPartial
#7
execPerpOps
#8
execPerpOps
#9
setData
#11
0x6a9b4698
#12
modifyLiquidities
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x67d846dd…358c
0x1489be…7777
2 touches
0 conflicts
0x0cc4c914…333b
0x34b655…2a6f
2 touches
0 conflicts
0x12a9b76e…cb76
0x3bd359…433a
2 touches
0 conflicts
0x44ed742f…63f5
0x3bd359…433a
2 touches
0 conflicts
0x4eb758b8…b13b
0x3bd359…433a
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
0x045532dd4b…244b7d
Audit this contract →
← previous block
·
next block →
recent activity