pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,670,887
← previous block
next block →
recent activity
Analyzing
Block #97,670,887
9 transactions · 9 stateful · 2026-08-20 16:24:21 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,670,887
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x5acec890
· blocks 3
#6
execFwdPositionOpsV2
#7
setData
#8
0x59558d29
#3
0x5acec890
· blocks 1
#5
execFwdPositionOpsV2
#4
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x574074d8…ccf9
0x34b655…2a6f
4 touches
1 conflict
0x2f67c85d…a080
0x34b655…2a6f
4 touches
1 conflict
0xc2108892…2b33
0x34b655…2a6f
4 touches
1 conflict
0x03a6363b…ad2b
0x34b655…2a6f
2 touches
0 conflicts
0x1a9f413e…1ee0
0x34b655…2a6f
2 touches
0 conflicts
0x2089053e…6c30
0x34b655…2a6f
2 touches
0 conflicts
0x2e4ef777…70ba
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
3 conflicts on slot
0xca841faae5…71486a
Audit this contract →
← previous block
·
next block →
recent activity