pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,356,260
← previous block
next block →
recent activity
Analyzing
Block #74,356,260
11 transactions · 9 stateful · 2026-05-13 16:27:30 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,356,260
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
redeemDelegations
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
setData
#6
handleOps
#8
forward
#9
0xb4b43d…a61b
#10
approve
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f2e60dc…e661
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2984cce8…2fe8
0x386489…7508
2 touches
0 conflicts
0x31e052ed…3133
0x386489…7508
2 touches
0 conflicts
0x544ac270…ab6b
0x3bd359…433a
2 touches
0 conflicts
0x12343646…129d
0x3ef3d8…d9ae
2 touches
0 conflicts
0x12343646…129e
0x3ef3d8…d9ae
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:
0x34b6552d…112a6f
1 conflict on slot
0x6f2e60dc1e…b5e661
Audit this contract →
← previous block
·
next block →
recent activity