pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,994,423
← previous block
next block →
recent activity
Analyzing
Block #72,994,423
9 transactions · 7 stateful · 2026-05-07 09:07:34 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,994,423
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
exactOutputSingle
#2
0x121eab2f
· blocks 1
#3
updateDataFeedsValuesPartial
#5
setData
#6
updatePosition
#7
forward
#8
0xeffdedb0
#4
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e5ebbf7…ae70
0xc8689a…ee79
4 touches
1 conflict
0x0175b7a6…1dbd
0x6ca43f…c331
4 touches
1 conflict
0x1a4b4152…0a08
0x6ca43f…c331
4 touches
1 conflict
0x3e4b8d9f…b8a7
0x6ca43f…c331
4 touches
1 conflict
0x5b3dfef8…a676
0x6ca43f…c331
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
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:
Perpl: Settlement / Helper
1 conflict on slot
0x4e5ebbf7fb…3fae70
Audit this contract →
← previous block
·
next block →
recent activity