pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,615,701
← previous block
next block →
recent activity
Analyzing
Block #74,615,701
10 transactions · 5 stateful · 2026-05-14 21:22:02 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,615,701
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
0x1094dc9f
#4
0x05ee6a22
#5
updateDataFeedsValuesPartial
#6
0x6a063d72
#7
setData
#8
0x0dc20f…cf8d
#9
0x89e690…d973
#2
0x0c7abd22
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
0x02edb942…eddd
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x9a0055d8…5702
0x065c9d…c394
2 touches
0 conflicts
0xffe431af…8faa
0x065c9d…c394
2 touches
0 conflicts
0x00f7e3b7…e015
0x188d58…ea8e
2 touches
0 conflicts
0x00f7e3b7…e016
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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:
0xd32edf66…9fff58
1 conflict on slot
0x02edb94297…c2eddd
Audit this contract →
← previous block
·
next block →
recent activity