pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,657,002
← previous block
next block →
recent activity
Analyzing
Block #74,657,002
14 transactions · 11 stateful · 2026-05-15 01:57:29 UTC
Parallelism
86
/100
Blocked
9
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,657,002
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
updatePrices
#6
addLiquidity
· blocks 1
#8
updateDataFeedsValuesPartial
#9
0x5339c59f
#10
0x5339c59f
#11
setData
#12
0x39435dac
#13
0x39435dac
#7
removeLiquidity
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x729c91b8…9537
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…953a
0x188d58…ea8e
2 touches
0 conflicts
0xffb76693…007a
0x188d58…ea8e
2 touches
0 conflicts
0xffb76693…007b
0x188d58…ea8e
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:
0x5afd3ec8…e77620
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity