pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,042,004
← previous block
next block →
recent activity
Analyzing
Block #73,042,004
12 transactions · 9 stateful · 2026-05-07 14:24:04 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,042,004
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
registerToken
#4
updatePrices
#5
0x5bf9264c
#6
0x5bf9264c
#7
updateDataFeedsValuesPartial
#9
0x765aeb4f
#10
relay
#11
setData
#2
0x0c7abd22
· blocks 1
#8
0x121eab2f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1526c23…f2bb
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x70b2f813…783c
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xecb99d47…07cf
0x065c9d…c394
3 touches
1 conflict
0xaec09a5e…fd69
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x8876d94c…8435
0x2a68ba…90c5
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
0xb1526c23fd…dbf2bb
Audit this contract →
← previous block
·
next block →
recent activity