pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,480,668
← previous block
next block →
recent activity
Analyzing
Block #73,480,668
12 transactions · 11 stateful · 2026-05-09 15:02:41 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,480,668
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
claimFee
#3
0x98717539
#4
forward
#5
0x39435dac
#6
updateDataFeedsValuesPartial
#7
0x5339c59f
· blocks 1
#9
0xed82b078
#10
setData
#11
0x39435dac
#8
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xcc770bdd…43ac
0x188d58…ea8e
2 touches
0 conflicts
0xcc770bdd…43ad
0x188d58…ea8e
2 touches
0 conflicts
0xed8fbefa…8155
0x188d58…ea8e
2 touches
0 conflicts
0xed8fbefa…8156
0x188d58…ea8e
2 touches
0 conflicts
0x20ac0567…c954
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity