pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,396,722
← previous block
next block →
recent activity
Analyzing
Block #73,396,722
10 transactions · 8 stateful · 2026-05-09 05:44:04 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,396,722
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x1094dc9f
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
0x0c7abd22
· blocks 1
#7
0x62be7533
#8
0xeffdedb0
#9
setData
#2
0x42dd8743
· blocks 1
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x59804329…9612
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0x1e66df36…64d1
0xa6afd3…d132
3 touches
1 conflict
0xf7ad0cb6…0416
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
0x2a68ba18…8e90c5
1 conflict on slot
0xc3c8642ae9…317da5
Audit this contract →
← previous block
·
next block →
recent activity