pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,485,280
← previous block
next block →
recent activity
Analyzing
Block #74,485,280
9 transactions · 8 stateful · 2026-05-14 06:46:16 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,485,280
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
#2
updateDataFeedsValuesPartial
#3
setData
#4
redeemDelegations
· blocks 1
#6
updatePriceFeedsIfNecessary
#7
0x6a05702f
#8
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
0xd0d0fd…4149
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xd82b3e68…dfee
0x1efe02…37d6
2 touches
0 conflicts
0x3dbd9177…e936
0xea1b8e…c5ec
2 touches
0 conflicts
0x41a75cd5…4527
0xea1b8e…c5ec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0xb6b74ae0…8d5e
0xea1b8e…c5ec
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:
0xd0d0fd53…e54149
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity