pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,425,547
← previous block
next block →
recent activity
Analyzing
Block #72,425,547
9 transactions · 6 stateful · 2026-05-04 17:57:28 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,425,547
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f8de80
#2
0x69f8de80
#3
0x3f5c179b
#4
updateDataFeedsValuesPartial
#5
0x69f8de80
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0f6f4f2…dffa
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3282f217…90ed
0x065c9d…c394
2 touches
0 conflicts
0x38b373f7…3109
0x065c9d…c394
2 touches
0 conflicts
0x558f4da9…1005
0x065c9d…c394
2 touches
0 conflicts
0xbe418c0e…3761
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:
0x34b6552d…112a6f
1 conflict on slot
0xd0f6f4f225…4cdffa
Audit this contract →
← previous block
·
next block →
recent activity