pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,046,131
← previous block
next block →
recent activity
Analyzing
Block #73,046,131
11 transactions · 10 stateful · 2026-05-07 14:51:35 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,046,131
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x05ee6a22
#2
0x05ee6a22
#3
0x5bf9264c
· blocks 1
#5
0x0c7abd22
· blocks 1
#7
0x6df9e92b
#8
updateDataFeedsValuesPartial
#9
0xeffdedb0
#10
setData
#4
0x5bf9264c
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0xf587a360…e9c1
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x036056…1881
2 touches
0 conflicts
0x1cd20063…86b2
0x036056…1881
2 touches
0 conflicts
0x2cf46a52…4116
0x036056…1881
2 touches
0 conflicts
0xa1a13fd6…b3af
0x036056…1881
2 touches
0 conflicts
0xb4691c32…4728
0x036056…1881
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:
Perpl
1 conflict on slot
0xc824469a90…af641c
Audit this contract →
← previous block
·
next block →
recent activity