pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,040,154
← previous block
next block →
recent activity
Analyzing
Block #106,040,154
28 transactions · 23 stateful · 2026-09-19 00:59:09 UTC
Parallelism
93
/100
Blocked
4
%
Avg conflicts / tx
0.04
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,040,154
· 28 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
execOrders
#4
updatePrices
#5
0x59558d29
#6
0x59558d29
#7
0x59558d29
#8
execPerpOps
· blocks 1
#10
execPerpOps
#11
execPerpOps
#12
updateDataFeedsValuesPartial
#13
executeBatch
#14
execFwdPositionOpsV2
#15
setData
#16
0x3f5c179b
#17
placeBet
#18
execOrders
#19
execOrders
#20
execOrders
#21
execOrders
#22
execOrders
#23
execOrders
#24
execOrders
#25
execOrders
#26
execOrders
#27
execOrders
#9
execPerpOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5e8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
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…001b
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
1 conflict on slot
0xe5bb3628b5…71e5e8
Audit this contract →
← previous block
·
next block →
recent activity