pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,387,109
← previous block
next block →
recent activity
Analyzing
Block #73,387,109
11 transactions · 9 stateful · 2026-05-09 04:40:05 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,387,109
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69febb1c
#2
0x69febb1c
#3
0x39435dac
#4
0x0c7abd22
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x54cb092e
#8
setData
#9
0xed82b078
#10
0xeffdedb0
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe26102f9…fed9
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x411b086e…1331
0x065c9d…c394
2 touches
0 conflicts
0x0429bf56…22cd
0x34b655…2a6f
2 touches
0 conflicts
0x2877f440…c2c8
0x34b655…2a6f
2 touches
0 conflicts
0x6656fcdb…9235
0x34b655…2a6f
2 touches
0 conflicts
0x8a2657f5…e008
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
1 conflict on slot
0xe26102f957…1efed9
Audit this contract →
← previous block
·
next block →
recent activity