pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,333,960
← previous block
next block →
recent activity
Analyzing
Block #73,333,960
9 transactions · 8 stateful · 2026-05-08 22:46:33 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,333,960
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x121eab2f
· blocks 1
#6
0x69fe6841
#7
0xeffdedb0
#8
setData
#5
0x121eab2f
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
0xd821ae10…fe17
0xc8689a…ee79
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0xbdff944d…447e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x120182c5…1647
0x065c9d…c394
3 touches
1 conflict
0x00000000…000b
0xaba216…a862
3 touches
1 conflict
0x2e2214a9…fe0d
0xaba216…a862
3 touches
1 conflict
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:
0xc8689a47…62ee79
1 conflict on slot
0xd821ae106f…bcfe17
Audit this contract →
← previous block
·
next block →
recent activity