pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,201,467
← previous block
next block →
recent activity
Analyzing
Block #73,201,467
10 transactions · 9 stateful · 2026-05-08 08:05:08 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,201,467
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
swap
#3
0x98717539
· blocks 1
#4
updatePriceFeedsIfNecessary
#5
updateDataFeedsValuesPartial
#6
0x69fd99ac
#7
0xeffdedb0
#8
setData
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
4 touches
1 conflict
0x602ff3d4…3ebd
0x34b655…2a6f
4 touches
1 conflict
0xac8e97a0…8426
0x34b655…2a6f
4 touches
1 conflict
0x8476b57c…5527
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0xd996735f…8730
0x1b6862…e19c
2 touches
0 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
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:
0x34b6552d…112a6f
1 conflict on slot
0x388e001a16…e57e04
Audit this contract →
← previous block
·
next block →
recent activity