pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,213,400
← previous block
next block →
recent activity
Analyzing
Block #72,213,400
10 transactions · 9 stateful · 2026-05-03 18:19:16 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,213,400
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f7921c
#2
updatePrices
#3
0x9036287a
· blocks 1
#4
updateDataFeedsValuesPartial
#6
0x6df9e92b
· blocks 1
#8
setData
#9
0x39435dac
#5
0x3f5c179b
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0x5e1b1a…7777
4 touches
1 conflict
0x4d1acd7c…f345
0x5e1b1a…7777
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x75c3ab…4f0d
4 touches
1 conflict
0x00000000…0001
0x75c3ab…4f0d
4 touches
1 conflict
0x4341432b…ad29
0x065c9d…c394
4 touches
1 conflict
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity