pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,509,657
← previous block
next block →
recent activity
Analyzing
Block #97,509,657
13 transactions · 12 stateful · 2026-08-20 02:43:44 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,509,657
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0xab083028
#3
execOrder
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOpsV2
#7
claim
· blocks 1
#9
execFwdPositionOpsV2
#10
0x59558d29
#11
execOrders
#12
execOrders
#8
0xc925b3a5
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfbce51b…b7bd
0x8964d7…10f8
4 touches
1 conflict
0x2a07e64e…fe77
0x754704…b603
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0xbfbce51b…b7be
0x8964d7…10f8
3 touches
1 conflict
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x2d8487d0…24c6
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x6235fbc3…aa1e
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:
0x8964d7c9…5b10f8
1 conflict on slot
0xbfbce51b65…52b7bd
Audit this contract →
← previous block
·
next block →
recent activity