pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,202,073
← previous block
next block →
recent activity
Analyzing
Block #73,202,073
8 transactions · 7 stateful · 2026-05-08 08:09:10 UTC
Parallelism
75
/100
Blocked
29
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,202,073
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x69fd9a9e
#6
0xeffdedb0
#7
setData
#2
0x0c7abd22
#3
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xda6b535e…6d69
0x1b6862…e19c
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x9abd5f14…7eb7
0xd32edf…ff58
3 touches
1 conflict
0x596dc94b…e09e
0x065c9d…c394
2 touches
0 conflicts
0x74b8ae67…db3c
0x065c9d…c394
2 touches
0 conflicts
0x7f189cf6…afab
0x065c9d…c394
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000015
Audit this contract →
← previous block
·
next block →
recent activity