pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,423,721
← previous block
next block →
recent activity
Analyzing
Block #74,423,721
10 transactions · 9 stateful · 2026-05-13 23:56:32 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,423,721
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
updatePrices
#3
0x39435dac
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x6a051028
#7
setData
#8
redeemDelegations
· blocks 1
#4
0x98717539
#9
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x0b07e4…e820
4 touches
1 conflict
0xbad68552…e6bf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x2dc19055…17c8
0x065c9d…c394
2 touches
0 conflicts
0x8adc5ee8…0d73
0x065c9d…c394
2 touches
0 conflicts
0xdae233d2…8e95
0x065c9d…c394
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:
0x0b07e4a4…bae820
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity