pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,601,813
← previous block
next block →
recent activity
Analyzing
Block #73,601,813
10 transactions · 9 stateful · 2026-05-10 04:28:01 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,601,813
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0xc5a04723
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x5339c59f
· blocks 1
#8
0x5339c59f
#9
setData
#2
updatePrices
#7
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x90e67c86…3786
0x1001ff…1001
2 touches
0 conflicts
0xc6f1b3af…c97c
0x1001ff…1001
2 touches
0 conflicts
0x00000000…0000
0x276664…5732
2 touches
0 conflicts
0x00000000…0002
0x276664…5732
2 touches
0 conflicts
0x00000000…0004
0x276664…5732
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity