pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,529,140
← previous block
next block →
recent activity
Analyzing
Block #97,529,140
14 transactions · 10 stateful · 2026-08-20 04:21:45 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,529,140
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98269401
#2
0xa96df62f
#3
0x41a8f47c
· blocks 1
#4
0x41a8f47c
#5
0x41a8f47c
#6
matchOrders
#7
setData
#9
0x6ad2e98b
#10
0xab083028
#11
updateDataFeedsValuesPartial
#12
execFwdPositionOpsV2
#13
0x59558d29
#8
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x93d70dba…0574
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0003
0x103de0…bb55
2 touches
0 conflicts
0x00000000…0005
0x103de0…bb55
2 touches
0 conflicts
0x0778475b…bd75
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0000
0x33a247…6221
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:
0x103de0b5…25bb55
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity