pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,197,831
← previous block
next block →
recent activity
Analyzing
Block #97,197,831
12 transactions · 8 stateful · 2026-08-19 00:02:56 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,197,831
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
0xdb834625
#3
0x6ad2e98b
#4
updateDataFeedsValuesPartial
#5
0x5acec890
#6
execFwdPositionOpsV2
· blocks 1
#7
batchUpdate
#9
setData
#10
0x0550e1…fbe6
#11
0x546f4a…ed1e
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69e36c95…2866
0x34b655…2a6f
4 touches
1 conflict
0x8329c51e…4064
0x34b655…2a6f
4 touches
1 conflict
0x8329c51e…4065
0x34b655…2a6f
4 touches
1 conflict
0xa287ca33…9a13
0x34b655…2a6f
4 touches
1 conflict
0x434587c7…2645
0x34b655…2a6f
4 touches
1 conflict
0xe9662735…4f99
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
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
0x69e36c95bb…492866
Audit this contract →
← previous block
·
next block →
recent activity