pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,565,849
← previous block
next block →
recent activity
Analyzing
Block #74,565,849
9 transactions · 9 stateful · 2026-05-14 15:48:15 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,565,849
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5de3085d
· blocks 1
#3
0x1ffa3c9b
#4
updatePrices
#5
updateDataFeedsValuesPartial
#6
setData
#7
redeemDelegations
#8
0x39435dac
#2
0x9025acd4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xa7283d…0ace
4 touches
1 conflict
0x536e2740…61ac
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x24cc7fc7…fa3a
0x065c9d…c394
2 touches
0 conflicts
0xc17bf20f…8c64
0x065c9d…c394
2 touches
0 conflicts
0xc75e1ae3…9b48
0x065c9d…c394
2 touches
0 conflicts
0x8fa7a69c…8fd7
0x46bd38…7777
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:
0xa7283d07…f90ace
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity