pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,260,524
← previous block
next block →
recent activity
Analyzing
Block #74,260,524
10 transactions · 8 stateful · 2026-05-13 05:50:43 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,260,524
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x39435dac
· blocks 1
#4
0x5bf9264c
#5
0x5bf9264c
#7
0x5339c59f
#8
setData
#9
0x39435dac
#6
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x664bf99e…0a8c
0x34b655…2a6f
4 touches
1 conflict
0xfd61c11e…ec09
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0c1aa307…ff9c
0x34b655…2a6f
2 touches
0 conflicts
0x25de453d…9573
0x34b655…2a6f
2 touches
0 conflicts
0x36e47e18…87de
0x34b655…2a6f
2 touches
0 conflicts
0x897bb34b…bab0
0x34b655…2a6f
2 touches
0 conflicts
0xac2a0273…721b
0x34b655…2a6f
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:
0x34b6552d…112a6f
1 conflict on slot
0x664bf99ec8…ec0a8c
Audit this contract →
← previous block
·
next block →
recent activity