pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,826,196
← previous block
next block →
recent activity
Analyzing
Block #97,826,196
12 transactions · 12 stateful · 2026-08-21 05:30:36 UTC
Parallelism
83
/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,826,196
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
· blocks 1
#4
0x3f5c179b
#5
0x3f5c179b
#6
0x3f5c179b
#7
0x57368ddf
#8
execFwdPositionOpsV2
#9
setData
#10
0x59558d29
#11
execOrders
#3
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe38f7c29…72fc
0x34b655…2a6f
4 touches
1 conflict
0xcf10b6c3…c186
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x103e4080…0d3a
0x34b655…2a6f
2 touches
0 conflicts
0x117d8fd8…6df6
0x34b655…2a6f
2 touches
0 conflicts
0x61a46e28…ec92
0x34b655…2a6f
2 touches
0 conflicts
0x699c6386…f7ba
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
0xe38f7c29b3…7472fc
Audit this contract →
← previous block
·
next block →
recent activity