pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,576,195
← previous block
next block →
recent activity
Analyzing
Block #72,576,195
9 transactions · 8 stateful · 2026-05-05 10:40:36 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,576,195
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x9036287a
· blocks 1
#3
0x98717539
#4
redeemDelegations
#6
updateDataFeedsValuesPartial
#7
cancelLimitOrder
#8
setData
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x88037a63…fd9b
0x065c9d…c394
4 touches
1 conflict
0x99712ab4…a92a
0x065c9d…c394
3 touches
1 conflict
0x3b4d66b6…d0db
0x065c9d…c394
3 touches
1 conflict
0x17c055e3…e401
0x065c9d…c394
3 touches
1 conflict
0x3cdd00c4…f222
0x065c9d…c394
2 touches
0 conflicts
0x98fea9e8…1bad
0x065c9d…c394
2 touches
0 conflicts
0xbbee74c2…567a
0x065c9d…c394
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity