pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,497,521
← previous block
next block →
recent activity
Analyzing
Block #73,497,521
9 transactions · 9 stateful · 2026-05-09 16:54:52 UTC
Parallelism
78
/100
Blocked
33
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,497,521
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69ff6754
· blocks 1
#2
updatePrices
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x98717539
· blocks 1
#7
setData
#3
updatePrices
#6
0x98717539
#8
0x69ff6754
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
5
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x468c69b1…af11
0x8d66a4…3095
4 touches
1 conflict
0x7f430e47…4cbd
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a9
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x5d70606a…1d53
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:
Perpl
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity