pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,035,096
← previous block
next block →
recent activity
Analyzing
Block #73,035,096
10 transactions · 10 stateful · 2026-05-07 13:38:07 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,035,096
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x69fc9636
#4
updateDataFeedsValuesPartial
#5
0x121eab2f
#6
setData
#7
0x9e76c652
#8
forward
#9
0xeffdedb0
#2
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x13ec2e25…1f81
0x065c9d…c394
2 touches
0 conflicts
0x1c25f4ef…8101
0x065c9d…c394
2 touches
0 conflicts
0x5be153c8…6d9e
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:
0xd574cae5…037ab1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity