pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,396,271
← previous block
next block →
recent activity
Analyzing
Block #73,396,271
10 transactions · 9 stateful · 2026-05-09 05:41:03 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,396,271
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x69fec967
#4
0xe9316489
· blocks 1
#6
0xeffdedb0
#7
setData
#8
0x39435dac
#9
0x39435dac
#5
0xe9316489
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b7b5759…b3b3
0x96b79e…d00a
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
2 touches
0 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
2 touches
0 conflicts
0xfd784183…67bb
0x34b655…2a6f
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
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:
0x96b79ef4…d2d00a
1 conflict on slot
0x2b7b575976…c5b3b3
Audit this contract →
← previous block
·
next block →
recent activity