pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,213,383
← previous block
next block →
recent activity
Analyzing
Block #72,213,383
9 transactions · 9 stateful · 2026-05-03 18:19:10 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,213,383
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x9036287a
· blocks 1
#3
0x98717539
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
updatePriceFeedsIfNecessary
#4
0x98717539
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ab
0x8d66a4…3095
4 touches
1 conflict
0xe72962f6…e169
0x8d66a4…3095
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0ce83d69…1960
0x065c9d…c394
2 touches
0 conflicts
0x2928d1ee…75da
0x065c9d…c394
2 touches
0 conflicts
0x39aae24d…6260
0x065c9d…c394
2 touches
0 conflicts
0x8a5c8331…8e29
0x065c9d…c394
2 touches
0 conflicts
0xaead6ee6…0058
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:
0x8d66a43f…113095
1 conflict on slot
0x8a35acfbc1…6bd1ab
Audit this contract →
← previous block
·
next block →
recent activity