pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,631,395
← previous block
next block →
recent activity
Analyzing
Block #74,631,395
14 transactions · 13 stateful · 2026-05-14 23:06:39 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,631,395
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a0655f6
· blocks 1
#3
setPrice
#4
setPrice
#5
setPrice
#6
setPrice
#7
setPrice
#8
setPrice
#9
updatePrices
#10
updateDataFeedsValuesPartial
#11
updateDataFeedsValuesPartial
#12
setData
#13
0x39435dac
#2
0x6a0655f7
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
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x2b36ecc6…093e
0x3c2269…cf62
2 touches
0 conflicts
0x634f554f…186c
0x3c2269…cf62
2 touches
0 conflicts
0x78b6c319…bac0
0x3c2269…cf62
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