pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,986,339
← previous block
next block →
recent activity
Analyzing
Block #98,986,339
8 transactions · 8 stateful · 2026-08-25 07:37:54 UTC
Parallelism
50
/100
Blocked
38
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,986,339
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#3
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#2
0x0c7abd22
· blocks 2
#4
0x0c7abd22
· blocks 1
#5
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
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7eee7241…8436
0xd32edf…ff58
7 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x50291c7f…f59c
0x065c9d…c394
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065e
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
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
6 conflicts on slot
0x7eee724146…5f8436
Audit this contract →
← previous block
·
next block →
recent activity