pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,501,484
← previous block
next block →
recent activity
Analyzing
Block #72,501,484
9 transactions · 8 stateful · 2026-05-05 02:23:07 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,501,484
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updatePosition
#3
0x3f5c179b
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0xed82b078
· blocks 1
#7
0x69f95503
#8
setData
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xa27fa22d…7dca
0x54cd53…9e7d
2 touches
0 conflicts
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x0b74c3ca…5d97
0x6657d1…8ccc
2 touches
0 conflicts
0x0cc89880…ea71
0x6657d1…8ccc
2 touches
0 conflicts
0x395f710f…309f
0x6657d1…8ccc
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