pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,628,563
← previous block
next block →
recent activity
Analyzing
Block #97,628,563
9 transactions · 9 stateful · 2026-08-20 12:44:57 UTC
Parallelism
44
/100
Blocked
44
%
Avg conflicts / tx
1.11
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,628,563
· 9 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x0c7abd22
· blocks 4
#3
matchOrders
#7
forward
#8
execFwdPositionOpsV2
#2
0x0c7abd22
· blocks 3
#4
0x0c7abd22
· blocks 2
#5
0x0c7abd22
· blocks 1
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
5
w3
6
w4
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe61bb73c…366e
0xd32edf…ff58
9 touches
10 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3b49be75…3557
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
0x065c9d…c394
2 touches
0 conflicts
0x9a3e90bd…6ef0
0x065c9d…c394
2 touches
0 conflicts
0xdfa159d0…1576
0x065c9d…c394
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:
FastLane: FastLaneAuctionHandler
10 conflicts on slot
0xe61bb73c0f…85366e
Audit this contract →
← previous block
·
next block →
recent activity