pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,524,647
← previous block
next block →
recent activity
Analyzing
Block #73,524,647
8 transactions · 6 stateful · 2026-05-09 19:55:18 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,524,647
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
poke
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x39435dac
· blocks 1
#6
0x39435dac
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac206e47…ef7d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b998a39…39c4
0x065c9d…c394
2 touches
0 conflicts
0x1238ab7c…1885
0x065c9d…c394
2 touches
0 conflicts
0x3670a7bb…890b
0x065c9d…c394
2 touches
0 conflicts
0x421d6551…436c
0x065c9d…c394
2 touches
0 conflicts
0x49434069…2a74
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:
0x34b6552d…112a6f
1 conflict on slot
0xac206e4761…ffef7d
Audit this contract →
← previous block
·
next block →
recent activity