pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,651,516
← previous block
next block →
recent activity
Analyzing
Block #73,651,516
13 transactions · 8 stateful · 2026-05-10 10:01:21 UTC
Parallelism
85
/100
Blocked
25
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,651,516
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updatePrices
#4
0x39435dac
· blocks 1
#5
0x5bf9264c
#6
0xe7be4706
#7
0xe7be4706
#8
0xe7be4706
#9
updateDataFeedsValuesPartial
#10
0x6a0057e9
#11
setData
#2
0xef555769
#12
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38524fae…9deb
0x34b655…2a6f
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x10c0f1ff…a3f5
0x111111…db61
2 touches
0 conflicts
0x9835db2a…294b
0x111111…db61
2 touches
0 conflicts
0xcb78f92f…9d79
0x111111…db61
2 touches
0 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
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
0x38524faed4…ae9deb
Audit this contract →
← previous block
·
next block →
recent activity