pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,503,552
← previous block
next block →
recent activity
Analyzing
Block #73,503,552
9 transactions · 8 stateful · 2026-05-09 17:35:06 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,503,552
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
instantRedeem
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x5339c59f
· blocks 2
#7
0x69ff70c2
#8
setData
#5
0x5339c59f
· blocks 1
#6
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x52c63247…ce02
0x32a6e1…d85b
2 touches
0 conflicts
0x8a6710f3…ce5c
0x32a6e1…d85b
2 touches
0 conflicts
0x10814d14…cdda
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x57de3828…3fbb
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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity