pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,795,818
← previous block
next block →
recent activity
Analyzing
Block #73,795,818
10 transactions · 9 stateful · 2026-05-11 02:15:03 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,795,818
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
relay
#4
claim
· blocks 2
#7
0x6a013c1f
#8
setData
#9
0x39435dac
#5
merklClaim
· blocks 1
#6
claim
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x544ac270…ab6b
0x3bd359…433a
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xdd5dd18a…fdb2
0x3e4f2b…ba84
2 touches
0 conflicts
0xb1194e9f…34d9
0x3ef3d8…d9ae
2 touches
0 conflicts
0xb1194e9f…34da
0x3ef3d8…d9ae
2 touches
0 conflicts
0xbf510395…ad62
0x3ef3d8…d9ae
2 touches
0 conflicts
0xbf510395…ad63
0x3ef3d8…d9ae
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:
0x3bd359c1…15433a
3 conflicts on slot
0x544ac27000…59ab6b
Audit this contract →
← previous block
·
next block →
recent activity