pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,502,696
← previous block
next block →
recent activity
Analyzing
Block #73,502,696
9 transactions · 8 stateful · 2026-05-09 17:29:23 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,502,696
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x76368669
· blocks 1
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
withdraw
#6
0x69ff6f6a
#7
setData
#8
0x39435dac
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
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
0x066ee0c4…f3d6
0x065c9d…c394
2 touches
0 conflicts
0x1c90f748…9418
0x065c9d…c394
2 touches
0 conflicts
0x60b24061…7c23
0x188d58…ea8e
2 touches
0 conflicts
0x60b24061…7c25
0x188d58…ea8e
2 touches
0 conflicts
0x60b24061…7c26
0x188d58…ea8e
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity