pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,738,951
← previous block
next block →
recent activity
Analyzing
Block #97,738,951
9 transactions · 9 stateful · 2026-08-20 22:10:08 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,738,951
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
transfer
#2
exactOutputSingle
#3
0x6ad2e98b
#4
execOrders
#5
execOrder
· blocks 2
#8
0x0c7abd22
#6
execOrder
· blocks 1
#7
execOrder
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69352f9f…5449
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x356e99d6…f048
0x34b655…2a6f
2 touches
0 conflicts
0x3c78ca04…432c
0x34b655…2a6f
2 touches
0 conflicts
0x5256b248…5624
0x34b655…2a6f
2 touches
0 conflicts
0x7f38bfbc…61e3
0x34b655…2a6f
2 touches
0 conflicts
0xae762af9…0f84
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
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
0x69352f9f62…375449
Audit this contract →
← previous block
·
next block →
recent activity