pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,429,363
← previous block
next block →
recent activity
Analyzing
Block #72,429,363
9 transactions · 8 stateful · 2026-05-04 18:22:50 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,429,363
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f8e472
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
· blocks 1
#4
0x96e62922
#5
forward
#6
0xed82b078
· blocks 1
#8
setData
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x0c1bcb2c…5eff
0x065c9d…c394
2 touches
0 conflicts
0x46d453f2…644b
0x065c9d…c394
2 touches
0 conflicts
0x518100e6…64e8
0x065c9d…c394
2 touches
0 conflicts
0xa480e389…ff4a
0x065c9d…c394
2 touches
0 conflicts
0x00000000…000b
0x2a347b…e9d3
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
0xffe431af56…838faa
Audit this contract →
← previous block
·
next block →
recent activity