pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,524,671
← previous block
next block →
recent activity
Analyzing
Block #73,524,671
11 transactions · 9 stateful · 2026-05-09 19:55:28 UTC
Parallelism
64
/100
Blocked
33
%
Avg conflicts / tx
0.55
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,524,671
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
#2
0x1094dc9f
#3
updateDataFeedsValuesPartial
#4
0x98717539
#5
0x5339c59f
· blocks 3
#9
0x69ff91a7
#10
setData
#6
0xed82b078
· blocks 2
#7
0xed82b078
· blocks 1
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
7
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xf2e6db09…b180
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x9b334941…fddb
0x1b6862…e19c
2 touches
0 conflicts
0xc9e97522…3519
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:
0x2a68ba18…8e90c5
6 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity