pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,041,840
← previous block
next block →
recent activity
Analyzing
Block #73,041,840
9 transactions · 8 stateful · 2026-05-07 14:22:58 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,041,840
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 2
#4
forward
#5
updateTemporalNumericValuesV1
#6
updateDataFeedsValuesPartial
#7
0xeffdedb0
#8
setData
#2
updatePrices
· blocks 1
#3
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x00000000…000b
0x2a347b…e9d3
2 touches
0 conflicts
0x1347c219…2e22
0xacc0a0…fd62
2 touches
0 conflicts
0x1632adac…6043
0xacc0a0…fd62
2 touches
0 conflicts
0x5250d39b…c3fb
0xacc0a0…fd62
2 touches
0 conflicts
0x58a1ffb8…36a0
0xacc0a0…fd62
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:
0xd574cae5…037ab1
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity