pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,973,983
← previous block
next block →
recent activity
Analyzing
Block #72,973,983
10 transactions · 10 stateful · 2026-05-07 06:51:19 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,973,983
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x121eab2f
#2
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
water
#6
setData
#7
forward
#8
updateTemporalNumericValuesV1
#9
0xeffdedb0
#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
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x7b50a82b…f53d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a8
0x8d66a4…3095
4 touches
1 conflict
0xcc6521c1…c892
0x8d66a4…3095
3 touches
1 conflict
0x61309372…5232
0x065c9d…c394
2 touches
0 conflicts
0x6c753ea9…ae13
0x065c9d…c394
2 touches
0 conflicts
0x79b45fd2…15ac
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:
Perpl
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity