pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,330,888
← previous block
next block →
recent activity
Analyzing
Block #99,330,888
10 transactions · 9 stateful · 2026-08-26 12:38:07 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,330,888
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xcf7468f4
#2
0xefdb8189
#3
execOrders
#4
0x0c7abd22
· blocks 2
#7
forward
#8
0xed82b078
#9
redeemDelegations
#5
0x0c7abd22
· blocks 1
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0be9646…8102
0xd32edf…ff58
5 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x00c43e68…2a3c
0x34b655…2a6f
2 touches
0 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
2 touches
0 conflicts
0x1b25f260…c429
0x34b655…2a6f
2 touches
0 conflicts
0x26d8622c…e8af
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:
FastLane: FastLaneAuctionHandler
3 conflicts on slot
0xe0be9646e9…5b8102
Audit this contract →
← previous block
·
next block →
recent activity