pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,374,932
← previous block
next block →
recent activity
Analyzing
Block #73,374,932
8 transactions · 6 stateful · 2026-05-09 03:19:05 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,374,932
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x80419567
#2
0x9cf9a051
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x69fea821
#7
0xddf7c2…7bb1
#3
0x9cf9a051
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b936aa5…05e3
0x141b1d…9583
4 touches
1 conflict
0x2b936aa5…05e5
0x141b1d…9583
4 touches
1 conflict
0x00000000…0002
0x08dd3d…a583
4 touches
1 conflict
0xff9eec93…1598
0x08dd3d…a583
4 touches
1 conflict
0xab39f3a1…b682
0x754704…b603
4 touches
1 conflict
0xdaaa2a2c…6609
0x754704…b603
4 touches
1 conflict
0x00000000…0003
0x2ae0cf…3d4e
4 touches
1 conflict
0x2b936aa5…05e2
0x141b1d…9583
4 touches
1 conflict
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:
0x141b1d9e…ab9583
1 conflict on slot
0x2b936aa586…6905e3
Audit this contract →
← previous block
·
next block →
recent activity