pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,223,905
← previous block
next block →
recent activity
Analyzing
Block #73,223,905
12 transactions · 9 stateful · 2026-05-08 10:34:26 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,223,905
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x121eab2f
#4
updateDataFeedsValuesPartial
#5
0x5bf9264c
#6
0x5bf9264c
#7
forward
#8
0x69fdbcaa
#9
0xeffdedb0
#10
setData
#11
0x34653439
#2
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x7378d785…e7dd
0x065c9d…c394
2 touches
0 conflicts
0x7dc4ebc6…9907
0x065c9d…c394
2 touches
0 conflicts
0x829c0589…3d33
0x065c9d…c394
2 touches
0 conflicts
0x915838a5…a619
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity