pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,218,005
← previous block
next block →
recent activity
Analyzing
Block #74,218,005
11 transactions · 7 stateful · 2026-05-13 01:08:07 UTC
Parallelism
73
/100
Blocked
29
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,218,005
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execute
#4
jMMeC
#6
0x5bf9264c
#7
0x5bf9264c
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#2
0x0c7abd22
· blocks 1
#5
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x4d928fa6…928a
0x065c9d…c394
3 touches
1 conflict
0x78ab106b…06d8
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xa6c3a97e…2d1b
0x065c9d…c394
2 touches
0 conflicts
0xc2e44c10…2db0
0x065c9d…c394
2 touches
0 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
2 touches
0 conflicts
0xe04293b6…f7b3
0x065c9d…c394
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
0x765c236f2d…b5ff45
Audit this contract →
← previous block
·
next block →
recent activity