pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,427,376
← previous block
next block →
recent activity
Analyzing
Block #74,427,376
15 transactions · 9 stateful · 2026-05-14 00:20:51 UTC
Parallelism
87
/100
Blocked
22
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,427,376
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
updatePrices
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
redeemDelegations
· blocks 1
#8
depositCollateral
#9
forward
#10
0x6a0515db
#11
setData
#12
jMMeC
#13
jMMeC
#14
jMMeC
#2
updatePrices
#7
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x4874bc…c117
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…000b
0x10da0c…e102
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x00000000…0036
0x386489…7508
2 touches
0 conflicts
0x19f920bc…6cfb
0x386489…7508
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:
0x4874bc3e…24c117
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity