pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,571,211
← previous block
next block →
recent activity
Analyzing
Block #72,571,211
10 transactions · 9 stateful · 2026-05-05 10:07:22 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,571,211
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
poke
#4
0x785f5745
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
setData
#9
0x39435dac
#2
updatePrices
#5
0x785f5745
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
0x00000000…0000
0xbab229…9388
4 touches
1 conflict
0x5860c4f3…0c39
0x3bd359…433a
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0x00000000…0003
0xbab229…9388
4 touches
1 conflict
0x490911cc…5fea
0x0c65a0…0852
4 touches
1 conflict
0x5d8dfaff…5b70
0x065c9d…c394
2 touches
0 conflicts
0x6f1536b2…e601
0x065c9d…c394
2 touches
0 conflicts
0x72a95f30…44da
0x065c9d…c394
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:
0xbab2296c…069388
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity