pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,401,761
← previous block
next block →
recent activity
Analyzing
Block #74,401,761
10 transactions · 8 stateful · 2026-05-13 21:30:27 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,401,761
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
setData
#4
redeemDelegations
· blocks 1
#6
0x0f6795d9
#7
0x0f6795d9
#8
0x6a04edea
#9
0x39435dac
#5
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x6b8a52…8e6c
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0de7749d…5bef
0x34b655…2a6f
2 touches
0 conflicts
0x234cc47b…a88e
0x34b655…2a6f
2 touches
0 conflicts
0x465b82d2…fa5a
0x34b655…2a6f
2 touches
0 conflicts
0x465b82d2…fa5b
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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:
0x6b8a52d9…918e6c
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity