pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,978,950
← previous block
next block →
recent activity
Analyzing
Block #72,978,950
11 transactions · 10 stateful · 2026-05-07 07:24:24 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,978,950
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x98717539
#2
updateDataFeedsValuesPartial
#3
0xb9b7b133
#4
0x0c7abd22
· blocks 2
#5
forward
#8
0x69fc3ea0
#9
0xeffdedb0
#10
setData
#6
0xed82b078
· blocks 1
#7
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w2
- 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
0x92a380a9…e8a5
0x065c9d…c394
4 touches
1 conflict
0x245a326a…699a
0x065c9d…c394
3 touches
1 conflict
0x68800d56…38b6
0x065c9d…c394
3 touches
1 conflict
0x8fd8faad…2d7c
0x065c9d…c394
3 touches
1 conflict
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x47c1a8e8…f74a
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
0x046a928e85…e50012
Audit this contract →
← previous block
·
next block →
recent activity