pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,285,817
← previous block
next block →
recent activity
Analyzing
Block #72,285,817
8 transactions · 5 stateful · 2026-05-04 02:25:55 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,285,817
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe0de3ed7
#2
updateDataFeedsValuesPartial
#3
0xccf50a51
#4
0x0c7abd22
· blocks 1
#5
0x3f5c179b
#6
setData
#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
0x19d4677e…92fa
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x8fe7508b…f855
0x065c9d…c394
2 touches
0 conflicts
0x9f3be336…c815
0x065c9d…c394
2 touches
0 conflicts
0xb5d8a737…6344
0x065c9d…c394
2 touches
0 conflicts
0xdbb56ff0…abf5
0x065c9d…c394
2 touches
0 conflicts
0xe532957e…7fa1
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:
0xd32edf66…9fff58
1 conflict on slot
0x19d4677e24…b392fa
Audit this contract →
← previous block
·
next block →
recent activity