pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,653,954
← previous block
next block →
recent activity
Analyzing
Block #73,653,954
11 transactions · 10 stateful · 2026-05-10 10:17:48 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
#73,653,954
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xed82b078
#2
updatePrices
#3
0x98717539
#4
updatePosition
#5
updateDataFeedsValuesPartial
#6
0x6a005bc4
#7
setData
#8
0x39435dac
· blocks 2
#9
0x39435dac
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6464996…3af9
0x34b655…2a6f
6 touches
3 conflicts
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a27f6fb…fa7f
0x065c9d…c394
2 touches
0 conflicts
0xb44d2267…c9b5
0x065c9d…c394
2 touches
0 conflicts
0x438cf5f6…f077
0x2a68ba…90c5
2 touches
0 conflicts
0x0711ec2d…d973
0x34b655…2a6f
2 touches
0 conflicts
0x1b9e654e…0a08
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:
0x34b6552d…112a6f
3 conflicts on slot
0xa6464996a2…6f3af9
Audit this contract →
← previous block
·
next block →
recent activity