pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,967,572
← previous block
next block →
recent activity
Analyzing
Block #73,967,572
10 transactions · 8 stateful · 2026-05-11 21:19:22 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,967,572
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updateDataFeedsValuesPartial
#3
0x98717539
#4
0xe7be4706
#5
0x62be7533
· blocks 1
#7
0x0f6795d9
#8
0x0f6795d9
#9
setData
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3870dbe…bef3
0x2a68ba…90c5
4 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1a84e266…4f8a
0x34b655…2a6f
2 touches
0 conflicts
0x2257be8c…d019
0x34b655…2a6f
2 touches
0 conflicts
0x41629728…ee69
0x34b655…2a6f
2 touches
0 conflicts
0x5b6af007…0f35
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
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
1 conflict on slot
0xb3870dbe63…c9bef3
Audit this contract →
← previous block
·
next block →
recent activity