pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,654,982
← previous block
next block →
recent activity
Analyzing
Block #73,654,982
11 transactions · 7 stateful · 2026-05-10 10:24:45 UTC
Parallelism
64
/100
Blocked
43
%
Avg conflicts / tx
0.36
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,654,982
· 11 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
0x1094dc9f
#5
updateDataFeedsValuesPartial
#6
claimLand
#8
forward
#9
setData
#10
jMMeC
#2
0x0c7abd22
· blocks 1
#3
0x0c7abd22
· blocks 1
#7
removeLiquidity
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x580c6fe7…0fe6
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x1eea1d7a…a808
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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:
0x1b68626d…2de19c
3 conflicts on slot
0x0000000000…000013
Audit this contract →
← previous block
·
next block →
recent activity