pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,446,500
← previous block
next block →
recent activity
Analyzing
Block #73,446,500
13 transactions · 10 stateful · 2026-05-09 11:15:21 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,446,500
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x121eab2f
#3
0x785f5745
· blocks 1
#5
forward
#6
updateDataFeedsValuesPartial
#7
0x5339c59f
· blocks 1
#9
0x69ff17c1
#10
0xd35dcd…76e0
#11
0x7baf27…2436
#12
setData
#4
0x785f5745
#8
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x490911cc…5fea
0x0c65a0…0852
4 touches
1 conflict
0x00000000…0000
0xbab229…9388
4 touches
1 conflict
0x00000000…0003
0xbab229…9388
4 touches
1 conflict
0x1dd505bf…9fd2
0x065c9d…c394
2 touches
0 conflicts
0x3e1bf8f7…8ff4
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
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity