pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,671,423
← previous block
next block →
recent activity
Analyzing
Block #73,671,423
9 transactions · 8 stateful · 2026-05-10 12:15:37 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,671,423
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x39435dac
#3
updateDataFeedsValuesPartial
#4
0x0c7abd22
· blocks 2
#5
0x54cb092e
#8
setData
#6
0x0c7abd22
· blocks 1
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e309cdd…8678
0xd32edf…ff58
5 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0x44039c64…0de6
0x34b655…2a6f
2 touches
0 conflicts
0x6c99893e…9c27
0x34b655…2a6f
2 touches
0 conflicts
0x6fbf2195…8660
0x34b655…2a6f
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:
0xd32edf66…9fff58
3 conflicts on slot
0x2e309cddee…bc8678
Audit this contract →
← previous block
·
next block →
recent activity