pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,781,852
← previous block
next block →
recent activity
Analyzing
Block #74,781,852
13 transactions · 8 stateful · 2026-05-15 15:51:15 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,781,852
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execute
#3
addLiquidity
#4
updateDataFeedsValuesPartial
#5
setData
#6
redeemDelegations
#7
forward
#8
0xed82b078
#9
0x6df9e92b
· blocks 1
#11
0x6a07416b
#12
0xb61241…45a9
#10
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x86dfd5…6a7d
4 touches
1 conflict
0x00000000…0001
0x86dfd5…6a7d
4 touches
1 conflict
0x1d4c90ab…1ba7
0xb72e62…7777
4 touches
1 conflict
0x44ad89ba…cf83
0xb72e62…7777
4 touches
1 conflict
0x1686502b…a1d2
0x3bd359…433a
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…000b
0xd3f273…09af
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
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity