pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,768,021
← previous block
next block →
recent activity
Analyzing
Block #74,768,021
13 transactions · 11 stateful · 2026-05-15 14:18:49 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,768,021
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a072bc0
#2
0x05ee6a22
#3
redeemDelegations
#4
collect
#5
forward
#6
forward
#7
0xed82b078
#8
0x6df9e92b
· blocks 1
#10
updateDataFeedsValuesPartial
#11
0x5339c59f
#12
setData
#9
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22882eec…bc8a
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x81550c…bba7
4 touches
1 conflict
0x00000000…0001
0x81550c…bba7
4 touches
1 conflict
0x44ad89ba…cf83
0xb744f5…7777
4 touches
1 conflict
0x67813250…9467
0xb744f5…7777
4 touches
1 conflict
0xbfe7fd3a…3168
0x3bd359…433a
2 touches
0 conflicts
0x11b5b289…debe
0x57ea24…2cec
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:
0x3bd359c1…15433a
1 conflict on slot
0x22882eecec…28bc8a
Audit this contract →
← previous block
·
next block →
recent activity