pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,480,825
← previous block
next block →
recent activity
Analyzing
Block #73,480,825
8 transactions · 6 stateful · 2026-05-09 15:03:43 UTC
Parallelism
63
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,480,825
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
setData
#3
updateDataFeedsValuesPartial
#6
0xed82b078
#7
0x69ff4d47
#4
0x5339c59f
· blocks 1
#5
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49c8cf6d…1118
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x4d2c1865…c0ba
0x065c9d…c394
3 touches
1 conflict
0x58432acf…7a0a
0x065c9d…c394
3 touches
1 conflict
0x2e4499b9…6d34
0x065c9d…c394
2 touches
0 conflicts
0x351df312…cf01
0x065c9d…c394
2 touches
0 conflicts
0x3544447f…1883
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
0x065c9d28…a9c394
1 conflict on slot
0x49c8cf6d0b…001118
Audit this contract →
← previous block
·
next block →
recent activity