pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,059,582
← previous block
next block →
recent activity
Analyzing
Block #102,059,582
14 transactions · 11 stateful · 2026-09-05 01:53:46 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,059,582
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0095142d
#2
execOrders
#3
0xa96df62f
#4
0x5acec890
#5
0x5acec890
#6
0x5acec890
#7
0x0c7abd22
· blocks 1
#8
0x59558d29
#9
0xb414539a
#10
setData
#11
0x62be7533
#12
0xc1f99bd0
#13
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94c711c1…9a2d
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3f1434d4…1ce1
0x11ed3b…2c96
2 touches
0 conflicts
0x9ba58458…a450
0x11ed3b…2c96
2 touches
0 conflicts
0x00000000…0000
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0002
0x2d59fc…cd50
2 touches
0 conflicts
0x00000000…0004
0x2d59fc…cd50
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
1 conflict on slot
0x94c711c13a…849a2d
Audit this contract →
← previous block
·
next block →
recent activity