pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,860,238
← previous block
next block →
recent activity
Analyzing
Block #72,860,238
11 transactions · 10 stateful · 2026-05-06 18:14:19 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,860,238
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x42dd8743
#2
0x121eab2f
#3
0x05ee6a22
#4
0x0c7abd22
· blocks 1
#5
updateDataFeedsValuesPartial
#7
forward
#8
0xeffdedb0
#9
setData
#10
0x69fb8572
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2984e56…9ac9
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3328a31d…ac41
0x065c9d…c394
2 touches
0 conflicts
0x6dc1d704…c5c0
0x065c9d…c394
2 touches
0 conflicts
0x7f189cf6…afab
0x065c9d…c394
2 touches
0 conflicts
0x96cd1f8a…5351
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:
0xd32edf66…9fff58
1 conflict on slot
0xe2984e566c…0b9ac9
Audit this contract →
← previous block
·
next block →
recent activity