pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,605,782
← previous block
next block →
recent activity
Analyzing
Block #97,605,782
12 transactions · 12 stateful · 2026-08-20 10:49:52 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,605,782
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
execOrder
· blocks 1
#5
settle
#6
setData
#7
updatePosition
#9
0x59558d29
#10
execOrders
#8
execFwdPositionOpsV2
#11
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
8
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e5cdd04…22ab
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x62bb4399…7734
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x327c57dd…836d
0x34b655…2a6f
2 touches
0 conflicts
0xa6b48d6e…0705
0x34b655…2a6f
2 touches
0 conflicts
0xec7d120d…7084
0x34b655…2a6f
2 touches
0 conflicts
0xfddc9a44…5163
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:
Perpl
1 conflict on slot
0x2e5cdd041a…6e22ab
Audit this contract →
← previous block
·
next block →
recent activity