pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,599,000
← previous block
next block →
recent activity
Analyzing
Block #74,599,000
12 transactions · 8 stateful · 2026-05-14 19:30:14 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,599,000
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a06233e
· blocks 1
#2
0x1ffa3c9b
· blocks 1
#3
0x6a06233e
#4
forward
#5
updateDataFeedsValuesPartial
#7
0x5339c59f
#9
setData
#10
0xfd9ffc…20cd
#11
0xa44ccc…58af
#6
0x5339c59f
#8
0x6a06233e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x77fc6d88…e906
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x077e4885…a945
0x065c9d…c394
2 touches
0 conflicts
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x69f9d47d…8b5c
0x065c9d…c394
2 touches
0 conflicts
0x7b42aaf0…a894
0x065c9d…c394
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:
0x681e908b…e1ae09
1 conflict on slot
0x0d622e34f9…000000
Audit this contract →
← previous block
·
next block →
recent activity