pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,454,290
← previous block
next block →
recent activity
Analyzing
Block #74,454,290
13 transactions · 9 stateful · 2026-05-14 03:20:02 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,454,290
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
updatePrices
#3
0x6a053fda
#4
commit
#5
updateDataFeedsValuesPartial
#6
0x5339c59f
#8
0xd483c4…07ce
#9
0x549378…f94a
#10
setData
#11
0x08f63d…948a
#12
0x39435dac
#7
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1f90c30f…fd38
0x065c9d…c394
2 touches
0 conflicts
0x819370a3…94ec
0x065c9d…c394
2 touches
0 conflicts
0xa4fb1a5a…9af5
0x065c9d…c394
2 touches
0 conflicts
0xefc240a0…dcd3
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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
0xffe431af56…838faa
Audit this contract →
← previous block
·
next block →
recent activity