pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,353,793
← previous block
next block →
recent activity
Analyzing
Block #74,353,793
8 transactions · 8 stateful · 2026-05-13 16:11:04 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,353,793
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
flash
· blocks 1
#2
updatePrices
#4
updateDataFeedsValuesPartial
#5
setData
#6
redeemDelegations
#7
0x39435dac
#3
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0xa6434442…babc
0x40c49f…2af0
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x08de772c…8e84
0x2a68ba…90c5
4 touches
1 conflict
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:
0x63e48b72…8c53f2
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity