pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,782,535
← previous block
next block →
recent activity
Analyzing
Block #74,782,535
13 transactions · 10 stateful · 2026-05-15 15:55:51 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,782,535
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6c05cd2b
· blocks 1
#3
0x5bf9264c
#4
0x5bf9264c
#5
forward
#6
forward
#7
forward
#8
updateDataFeedsValuesPartial
#9
setData
#10
redeemDelegations
#11
0x39435dac
#12
0x39435dac
#2
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x18aed20c…48f3
0x000000…012a
4 touches
1 conflict
0x00000000…0000
0xd5b70d…615b
4 touches
1 conflict
0x24fe818f…bb82
0x2cb31c…7777
2 touches
0 conflicts
0x4f3c51de…3f91
0x2cb31c…7777
2 touches
0 conflicts
0x9d8df255…f835
0x3bd359…433a
2 touches
0 conflicts
0xb4e825af…69e0
0x3bd359…433a
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
1 conflict on slot
0x7c403af1e6…1d31b1
Audit this contract →
← previous block
·
next block →
recent activity