pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,488,528
← previous block
next block →
recent activity
Analyzing
Block #73,488,528
10 transactions · 6 stateful · 2026-05-09 15:55:00 UTC
Parallelism
70
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,488,528
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
exactInputSingle
#2
0xed82b078
#3
0xed82b078
#4
0x5339c59f
· blocks 2
#6
0xed82b078
#8
setData
#9
0x39435dac
#5
0xed82b078
· blocks 1
#7
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x08ff97ee…2899
0x065c9d…c394
2 touches
0 conflicts
0x12c6301d…847e
0x065c9d…c394
2 touches
0 conflicts
0xa3f2f7bb…8a57
0x065c9d…c394
2 touches
0 conflicts
0xf537eaa0…73c8
0x065c9d…c394
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
3 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity