pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,356,136
← previous block
next block →
recent activity
Analyzing
Block #74,356,136
12 transactions · 8 stateful · 2026-05-13 16:26:41 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,356,136
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
0x6a04a6b8
#4
0x98717539
· blocks 1
#6
redeemDelegations
#7
forward
#8
0xed82b078
#9
setData
#10
0x708ef3…96fe
#11
0x0af0b8…454e
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x18a8cc8b…0633
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x4341432b…ad29
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
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:
0xc8689a47…62ee79
1 conflict on slot
0xc6417de023…802191
Audit this contract →
← previous block
·
next block →
recent activity