pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,394,843
← previous block
next block →
recent activity
Analyzing
Block #72,394,843
10 transactions · 10 stateful · 2026-05-04 14:32:50 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,394,843
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
· blocks 1
#3
0x785f5745
#4
0x0c7abd22
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x69f8ae89
#8
setData
#9
0x39435dac
#2
0x5bf9264c
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x68510731…6ac9
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5ae8d08e…204e
0x065c9d…c394
3 touches
1 conflict
0x32ba3492…ad85
0x065c9d…c394
3 touches
1 conflict
0xe5796bab…1b0d
0x065c9d…c394
2 touches
0 conflicts
0x490911cc…5fea
0x0c65a0…0852
2 touches
0 conflicts
0xcb3a850a…a18d
0x0c65a0…0852
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:
0x34b6552d…112a6f
1 conflict on slot
0xc824469a90…af641c
Audit this contract →
← previous block
·
next block →
recent activity