pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,774,864
← previous block
next block →
recent activity
Analyzing
Block #74,774,864
10 transactions · 7 stateful · 2026-05-15 15:04:37 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,774,864
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
exec
#4
depositNative
#5
updateDataFeedsValuesPartial
#6
0xf6e73e…e494
#7
0xf90ff2…77bb
#8
setData
#9
0x39435dac
#2
updatePrices
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
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0x6b44053f…754a
0x754704…b603
2 touches
0 conflicts
0x6e9b4ab5…a3eb
0x754704…b603
2 touches
0 conflicts
0x8f51630f…2ca9
0x754704…b603
2 touches
0 conflicts
0x9194f4a3…10b8
0x754704…b603
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity