pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,517,913
← previous block
next block →
recent activity
Analyzing
Block #74,517,913
12 transactions · 11 stateful · 2026-05-14 10:24:47 UTC
Parallelism
75
/100
Blocked
36
%
Avg conflicts / tx
0.42
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,517,913
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xed82b078
· blocks 2
#2
redeemDelegations
#3
0x6df9e92b
· blocks 2
#6
updateDataFeedsValuesPartial
#9
0x6a05a366
#10
setData
#11
withdraw
#4
0x6df9e92b
· blocks 1
#7
0x5339c59f
#8
0x5339c59f
#5
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w2
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0xc740dd24…9801
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x2c492d…444e
4 touches
1 conflict
0x00000000…0001
0x2c492d…444e
4 touches
1 conflict
0x44ad89ba…cf83
0x5df178…7777
4 touches
1 conflict
0x73131ffc…b46c
0x5df178…7777
4 touches
1 conflict
0x5a0a316d…ba8d
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
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:
0x3bd359c1…15433a
3 conflicts on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity