pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,462,457
← previous block
next block →
recent activity
Analyzing
Block #76,462,457
9 transactions · 8 stateful · 2026-05-23 10:49:51 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,462,457
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x0c7abd22
· blocks 2
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x024e5700
#8
0x39435dac
#3
0x0c7abd22
· blocks 1
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc1afcbe…4452
0xd32edf…ff58
5 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10abefc9…c9bc
0x1d1325…2305
2 touches
0 conflicts
0x10d80fee…dbda
0x1d1325…2305
2 touches
0 conflicts
0x14dfce82…e346
0x1d1325…2305
2 touches
0 conflicts
0x2f4b2cf9…4e1e
0x1d1325…2305
2 touches
0 conflicts
0x3426dbed…d278
0x1d1325…2305
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
0xdc1afcbe67…5b4452
Audit this contract →
← previous block
·
next block →
recent activity