pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,201,611
← previous block
next block →
recent activity
Analyzing
Block #73,201,611
12 transactions · 8 stateful · 2026-05-08 08:06:06 UTC
Parallelism
75
/100
Blocked
38
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,201,611
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
_makeSwaps
#4
0xe0de3ed7
#5
0xb264ae19
#7
updateDataFeedsValuesPartial
#9
0x69fd99e5
#10
0xeffdedb0
#11
setData
#2
0x0c7abd22
· blocks 2
#6
0x121eab2f
#8
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w2
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa711d889…70cd
0xd32edf…ff58
5 touches
3 conflicts
0xda3e10ac…fe49
0x065c9d…c394
4 touches
1 conflict
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0xe09eda07…8dda
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x91ad94df…ba1b
0x065c9d…c394
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
3 conflicts on slot
0xa711d889df…5d70cd
Audit this contract →
← previous block
·
next block →
recent activity