pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,310,066
← previous block
next block →
recent activity
Analyzing
Block #101,310,066
21 transactions · 19 stateful · 2026-09-02 10:56:31 UTC
Parallelism
86
/100
Blocked
21
%
Avg conflicts / tx
0.24
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,310,066
· 21 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
matchOrders
#4
0x6a980156
#5
0x5acec890
· blocks 3
#6
0x8263f5d9
#7
execOrders
#10
execPerpOps
#11
execPerpOps
#12
updateDataFeedsValuesPartial
#13
executeBatch
#14
transferWithAuthorization
· blocks 1
#16
setData
#17
execFwdPositionOpsV2
#18
0x3f5c179b
#19
transfer
#8
0x5acec890
· blocks 1
#15
transferWithAuthorization
#20
execOrders
#9
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
9
w2
14
w0
15
w1
20
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x6423fcab…a7c1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001d
0x1b6862…e19c
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
3 conflicts on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity