pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,387,568
← previous block
next block →
recent activity
Analyzing
Block #73,387,568
11 transactions · 10 stateful · 2026-05-09 04:43:07 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,387,568
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
execute
#3
updatePrices
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
commit
#7
0x5339c59f
#9
0xeffdedb0
#10
setData
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x46b31222…7b45
0x065c9d…c394
2 touches
0 conflicts
0x857defe7…ce74
0x065c9d…c394
2 touches
0 conflicts
0x8826a372…0888
0x065c9d…c394
2 touches
0 conflicts
0x9b661493…4b40
0x065c9d…c394
2 touches
0 conflicts
0xf61d41e3…e119
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity