pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,647,527
← previous block
next block →
recent activity
Analyzing
Block #73,647,527
7 transactions · 7 stateful · 2026-05-10 09:34:31 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,647,527
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x39435dac
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44d7acbf…e67d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x9a626f72…b404
0xd32edf…ff58
3 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x3b56c838…8a93
0x065c9d…c394
2 touches
0 conflicts
0x3db9f65b…c2f5
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
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:
0x1b68626d…2de19c
1 conflict on slot
0x44d7acbfe8…6ce67d
Audit this contract →
← previous block
·
next block →
recent activity