pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,818,097
← previous block
next block →
recent activity
Analyzing
Block #97,818,097
8 transactions · 8 stateful · 2026-08-21 04:49:39 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,818,097
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#2
execOrder
· blocks 2
#5
setData
#6
0x59558d29
#7
execOrders
#3
0x5acec890
· blocks 1
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7316dc00…c16a
0x34b655…2a6f
6 touches
3 conflicts
0xef9ee70c…19f5
0x34b655…2a6f
4 touches
1 conflict
0x4de40a98…ee65
0x34b655…2a6f
4 touches
1 conflict
0xbe6d0f1c…20a0
0x34b655…2a6f
4 touches
1 conflict
0x232b0b19…d946
0x34b655…2a6f
2 touches
0 conflicts
0x3d93ad2c…e747
0x34b655…2a6f
2 touches
0 conflicts
0xbfd18832…fd91
0x34b655…2a6f
2 touches
0 conflicts
0x5fad6fee…7714
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
0x7316dc00d3…b5c16a
Audit this contract →
← previous block
·
next block →
recent activity