pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,201,920
← previous block
next block →
recent activity
Analyzing
Block #73,201,920
7 transactions · 6 stateful · 2026-05-08 08:08:09 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,201,920
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xed82b078
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x39435dac
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x251861eb…78fd
0x34b655…2a6f
2 touches
0 conflicts
0x3b8ffd61…f3ad
0x34b655…2a6f
2 touches
0 conflicts
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0x417d4db1…e923
0x34b655…2a6f
2 touches
0 conflicts
0x840bf768…3d80
0x34b655…2a6f
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity