pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,226,235
← previous block
next block →
recent activity
Analyzing
Block #72,226,235
10 transactions · 8 stateful · 2026-05-03 19:45:26 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,226,235
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
· blocks 1
#4
0x3f5c179b
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x69f7a64e
#8
setData
#9
0x69f7a64e
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x8bdebcb2…781d
0x34b655…2a6f
2 touches
0 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
2 touches
0 conflicts
0x908d4442…2c4b
0x34b655…2a6f
2 touches
0 conflicts
0xb1856468…e84f
0x34b655…2a6f
2 touches
0 conflicts
0xc3aacf13…6b3d
0x34b655…2a6f
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