pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,482,762
← previous block
next block →
recent activity
Analyzing
Block #73,482,762
11 transactions · 10 stateful · 2026-05-09 15:16:36 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,482,762
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x52f07cf9
· blocks 1
#2
updatePrices
#3
multicall
#4
0x8f634cb9
#5
forward
#6
0x7c51d6cf
#8
updateDataFeedsValuesPartial
#9
0x69ff504c
#10
setData
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0009
0x32681b…919f
2 touches
0 conflicts
0x00000000…000c
0x32681b…919f
2 touches
0 conflicts
0x0789e797…0444
0x32681b…919f
2 touches
0 conflicts
0x0789e797…0445
0x32681b…919f
2 touches
0 conflicts
0x1063e8e2…aeed
0x32681b…919f
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:
0x3bd359c1…15433a
1 conflict on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity