pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,416,941
← previous block
next block →
recent activity
Analyzing
Block #74,416,941
13 transactions · 10 stateful · 2026-05-13 23:11:26 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,416,941
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xc4032d…4878
#2
jMMeC
#3
0xed82b078
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updatePrices
#6
get_block_hash_257335279069929
#7
0xec2bd3f2
#9
0x5339c59f
#10
0x6a050595
#11
setData
#12
0x39435dac
#8
0x5339c59f
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0001
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0003
0x019883…2a9a
2 touches
0 conflicts
0x00000000…0008
0x019883…2a9a
2 touches
0 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…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:
0x065c9d28…a9c394
1 conflict on slot
0x47b807a243…c53307
Audit this contract →
← previous block
·
next block →
recent activity