pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#72,498,654
← previous block
next block →
recent activity
Analyzing
Block #72,498,654
10 transactions · 8 stateful · 2026-05-05 02:04:18 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,498,654
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
claim
#2
0x0c7abd22
· blocks 1
#4
0x3f5c179b
#5
forward
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x69f9509a
#9
setData
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xa4e3b3b1…0911
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xab644955…4d9a
0xa6afd3…d132
3 touches
1 conflict
0xb89b6730…f738
0xd32edf…ff58
3 touches
1 conflict
0x4bef88e0…eaca
0x3bd359…433a
2 touches
0 conflicts
0x544ac270…ab6b
0x3bd359…433a
2 touches
0 conflicts
0xf607384a…2ca1
0x3ef3d8…d9ae
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:
0x1b68626d…2de19c
1 conflict on slot
0xcb45d9d62a…b1cb84
Audit this contract →
← previous block
·
next block →
recent activity