pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,697,542
← previous block
next block →
recent activity
Analyzing
Block #73,697,542
13 transactions · 10 stateful · 2026-05-10 15:11:52 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,697,542
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x54390b8b
· blocks 1
#2
0x719d975a
#3
0x77813803
#4
0x98717539
#5
updateDataFeedsValuesPartial
#6
setData
#7
redeemDelegations
#8
0x0c7abd22
· blocks 1
#9
0x62be7533
#12
0x8b23406f
#10
0x5339c59f
#11
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
8
w0
10
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x4d10fad4…b8e0
0x3bd359…433a
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0x5cca503f…2a22
0xd32edf…ff58
3 touches
1 conflict
0x264c6e4e…cbb6
0x3bd359…433a
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…0003
0x5afd3e…7620
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
0x0ac3194537…8f2c72
Audit this contract →
← previous block
·
next block →
recent activity