pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,923,214
← previous block
next block →
recent activity
Analyzing
Block #74,923,214
11 transactions · 9 stateful · 2026-05-16 07:34:19 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,923,214
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x39abec6b
#3
forward
#4
forward
#5
0xed82b078
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#9
0xa26ee4…2b6d
#10
redeemDelegations
#6
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00fd81f1…89ed
0x2ab50b…5c41
2 touches
0 conflicts
0x047d8971…c728
0x2ab50b…5c41
2 touches
0 conflicts
0x0f6fafe4…9688
0x2ab50b…5c41
2 touches
0 conflicts
0x1035ed1e…3885
0x2ab50b…5c41
2 touches
0 conflicts
0x132711dc…851a
0x2ab50b…5c41
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity