pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,041,920
← previous block
next block →
recent activity
Analyzing
Block #73,041,920
17 transactions · 7 stateful · 2026-05-07 14:23:30 UTC
Parallelism
88
/100
Blocked
14
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,041,920
· 17 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
#2
updatePrices
· blocks 1
#3
updatePrices
#4
updatePrices
#6
updatePrices
#7
updatePrices
#8
updatePrices
#9
updatePrices
#10
updatePrices
#11
updatePrices
#12
updatePrices
#13
updateDataFeedsValuesPartial
#14
0xeb8ce755
#15
0xeffdedb0
#16
setData
#5
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x67c5f21d…731f
0x0767c2…7777
2 touches
0 conflicts
0x690d790a…6b89
0x0767c2…7777
2 touches
0 conflicts
0x9f4577c5…f754
0x0767c2…7777
2 touches
0 conflicts
0xd189daf5…86ff
0x0767c2…7777
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
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity