pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,436,306
← previous block
next block →
recent activity
Analyzing
Block #73,436,306
9 transactions · 7 stateful · 2026-05-09 10:07:25 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,436,306
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#2
0xcf7468f4
#4
0x39435dac
#5
0x1a945f9c
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#3
0x0d484c28
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x846f2172…fd54
0x0555e3…2b9c
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0x46cb45de…a568
0x188d58…ea8e
4 touches
1 conflict
0x7f975651…8c28
0x0555e3…2b9c
2 touches
0 conflicts
0x8e80434a…a96d
0x0555e3…2b9c
2 touches
0 conflicts
0x00000000…0000
0x2d82ac…5fd8
2 touches
0 conflicts
0x00000000…0001
0x2d82ac…5fd8
2 touches
0 conflicts
0x00000000…0005
0x2d82ac…5fd8
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:
0x0555e30d…0d2b9c
1 conflict on slot
0x846f21722e…fdfd54
Audit this contract →
← previous block
·
next block →
recent activity