pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,575,785
← previous block
next block →
recent activity
Analyzing
Block #72,575,785
10 transactions · 9 stateful · 2026-05-05 10:37:52 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,575,785
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
· blocks 1
#1
updatePrices
#2
0x98717539
#4
0x3f5c179b
#5
updateDataFeedsValuesPartial
#6
0x69f9c8f8
#7
setData
#8
increaseLiquidity
#9
execute
#3
delegate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x0a000000…0000
0x000000…1000
2 touches
0 conflicts
0x0a000000…0001
0x000000…1000
2 touches
0 conflicts
0x0b000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3ce3d006…85fb
0x065c9d…c394
2 touches
0 conflicts
0x0de7749d…5bef
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:
0x00000000…001000
1 conflict on slot
0x0900000000…000007
Audit this contract →
← previous block
·
next block →
recent activity