pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,663,996
← previous block
next block →
recent activity
Analyzing
Block #73,663,996
11 transactions · 9 stateful · 2026-05-10 11:25:28 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,663,996
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a006ba0
#2
execute
#3
updatePrices
#4
0x39435dac
#5
exec
#6
updateDataFeedsValuesPartial
#7
0x98717539
· blocks 1
#8
0x6a006ba0
#9
setData
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x76498d82…2995
0x000000…012a
2 touches
0 conflicts
0x375b6201…9c1e
0x34b655…2a6f
2 touches
0 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
2 touches
0 conflicts
0x7c4e558b…e4b6
0x34b655…2a6f
2 touches
0 conflicts
0xa9988419…9f45
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:
0x34b6552d…112a6f
1 conflict on slot
0xa91c899f02…fa6ee3
Audit this contract →
← previous block
·
next block →
recent activity